Re: postgres slower on nested queries - Mailing list pgsql-general

From Martijn van Oosterhout
Subject Re: postgres slower on nested queries
Date
Msg-id 20070307115630.GD1482@svana.org
Whole thread Raw
In response to Re: postgres slower on nested queries  (Alexander Elgert <alexander_elgert@adiva.de>)
Responses Re: postgres slower on nested queries  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
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 cope with changes to the system catalogues. However, I
> >seem to remember some utility views that pgadmin uses that might be of
> >use.
> It would be nice to have the \d-query stored somewhere in the database.

Not really useful anyway. For the kind of trivial stuff you're doing
the queries will work for many many versions. 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.

Have a nice day,
--
Martijn van Oosterhout   <kleptog@svana.org>   http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.

Attachment

pgsql-general by date:

Previous
From: Devrim GÜNDÜZ
Date:
Subject: Re: real multi-master replication?
Next
From: Richard Huxton
Date:
Subject: Re: postgres slower on nested queries