Re: \d on database with a lot of tables is slow

From: "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>
To: Hannu Krosing <hannu(at)skype(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: \d on database with a lot of tables is slow
Date: 2005-09-26 18:17:42
Message-ID: 20050926181742.GP30974@pervasive.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Sep 25, 2005 at 10:10:22AM +0300, Hannu Krosing wrote:
> > Also, not sure if this matters, but they're occasionally getting errors
> > like 'Did not find relation named "table that exists"' (where 'table
> > that exists' is the name of some table that is in the catalog) from \d.
> > Does anyone know what causes that?
>
> mostly this happens on temp tables from other connections, which have
> managed to disappear by the time their detailed info is requested, and
> which would actually not show up in \d output due tu visibility checks.

They are seeing this doing \d on regular tables that won't be getting
deleted. Maybe there's some locking that should be happening but isn't?
Or maybe \d should be doing things in one statement instead of a bunch?
--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jim C. Nasby 2005-09-26 18:23:03 Re-run query on automatic reconnect
Previous Message Jim C. Nasby 2005-09-26 18:13:25 Re: Vacuum questions...