Revision 10375
Added by Aaron Marcuse-Kubitza over 11 years ago
| schemas/util.sql | ||
|---|---|---|
| 1201 | 1201 |
SELECT util._map(''"1"=>NULL, "2"=>NULL, "3"=>NULL, *=>*'', v) FROM unnest(array_fill(1, array[100000])) f (v)
|
| 1202 | 1202 |
and map_nulls()''s profiling query |
| 1203 | 1203 |
SELECT util.map_nulls(array[1, 2, 3]::text[], v) FROM unnest(array_fill(1, array[100000])) f (v) |
| 1204 |
both take ~920 ms'; |
|
| 1204 |
both take ~920 ms. |
|
| 1205 |
also, /inputs/REMIB/Specimen/postprocess.sql > country takes the same amount of time (56000 ms) to build with map_nulls() as with a literal hstore.'; |
|
| 1205 | 1206 |
|
| 1206 | 1207 |
|
| 1207 | 1208 |
-- |
Also available in: Unified diff
schemas/util.sql: map_nulls(): documented that inputs/REMIB/Specimen/postprocess.sql > country also shows that inlining is now happening properly. note that the speed improvement due to inlining is not as much, %
wise, when the values util._map() is run on are long strings instead of the short strings used in the initial profiling. this is because a greater % of the time is spent in system functions such as hstore>text, which are not affected by the inlining because they are run either way.