Dimitri Fontaine <dimi...@2ndquadrant.fr> writes: > For information, when we talk about performance problem, please note > that on my workstation with a default setup (not that it's important > here) we're talking about 86,420 ms for a loop of 100 > perform * from pg_extensions;
That's right, but > That displays 36 extensions and needs to parse their files twice and for > some of them need to scan the directory and parse other extension > control files before to get to the right one. Average less than 1ms to > do all that on my workstation, and typically less than 3ms if you > include psql side of things. That's not what happens, the pg_extensions() SRF will scan the directory once and parse each control file once, of course. I'm tired enough to mix the behaviour of finding the control file given *one* extension name at CREATE EXTENSION time with listing all available extensions. Sorry for the noise. In my mind though, the baseline remains the same. Now I will have a sleep and prepare for holidays, in some meaningful order… Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
