Re: [GENERAL] postgres slower on nested queries

2007-03-07 Thread Alexander Elgert
Tom Lane schrieb: Martijn van Oosterhout writes: ... Your real problem is that you're using the information_schema which has to do all sorts of extra work for standards compliance. If you don't need that you're going to be much better off just using the system catalogs. To put that in

Re: [GENERAL] postgres slower on nested queries

2007-03-07 Thread Tom Lane
Martijn van Oosterhout writes: > ... Your real problem is that > you're using the information_schema which has to do all sorts of extra > work for standards compliance. If you don't need that you're going to > be much better off just using the system catalogs. To put that in some perspective: re

Re: [GENERAL] postgres slower on nested queries

2007-03-07 Thread Richard Huxton
Alexander Elgert wrote: This results in a structure where I can itereate over all keys in the 2-dim array. You can see I iterate first over the databases and then over table AND columns! --- mysql: ~1s (Database X) --- postgres: ~1s (Database Y) ;) In contrast: ==

Re: [GENERAL] postgres slower on nested queries

2007-03-07 Thread Martijn van Oosterhout
On Wed, Mar 07, 2007 at 12:12:52PM +0100, Alexander Elgert wrote: > >Nope - \d is psql only. That's because what it does changes with the > >system catalogues. If you want a stable representation, use the > >information_schema. If you want all the PostgreSQL-specific details > >you'll have to co

Re: [GENERAL] postgres slower on nested queries

2007-03-07 Thread Alexander Elgert
Richard Huxton schrieb: Alexander Elgert wrote: Hello, I programmed a little script which iterates over all databases in a DBMS, iterating over all tables and then over all columns. This skript works for mysql and postgres. 1. Solution overview foreach database { for

Re: [GENERAL] postgres slower on nested queries

2007-03-07 Thread Richard Huxton
Tom Lane wrote: Richard Huxton writes: Alexander Elgert wrote: I found the postgres version VERY slow, so a decided to fetch Define VERY - it took what, milliseconds to do this? Seconds? Hours? I think he's complaining that the standards-conformant view in Postgres is slower than the spec

Re: [GENERAL] postgres slower on nested queries

2007-03-06 Thread Tom Lane
Richard Huxton writes: > Alexander Elgert wrote: >> I found the postgres version VERY slow, so a decided to fetch > Define VERY - it took what, milliseconds to do this? Seconds? Hours? I think he's complaining that the standards-conformant view in Postgres is slower than the specialized SHOW com

Re: [GENERAL] postgres slower on nested queries

2007-03-06 Thread Richard Huxton
Alexander Elgert wrote: Hello, I programmed a little script which iterates over all databases in a DBMS, iterating over all tables and then over all columns. This skript works for mysql and postgres. 1. Solution overview foreach database { foreach table { forea

[GENERAL] postgres slower on nested queries

2007-03-06 Thread Alexander Elgert
Hello, I programmed a little script which iterates over all databases in a DBMS, iterating over all tables and then over all columns. This skript works for mysql and postgres. 1. Solution overview foreach database { foreach table { foreach column { do