Re: \d on database with a lot of tables is slow - Mailing list pgsql-hackers

From Jim C. Nasby
Subject Re: \d on database with a lot of tables is slow
Date
Msg-id 20050926181742.GP30974@pervasive.com
Whole thread Raw
In response to Re: \d on database with a lot of tables is slow  (Hannu Krosing <hannu@skype.net>)
List 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@pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461


pgsql-hackers by date:

Previous
From: "Jim C. Nasby"
Date:
Subject: Re: Vacuum questions...
Next
From: "Jim C. Nasby"
Date:
Subject: Re: Vacuum questions...