Re: Re: [GENERAL] pgstattuple triggered checkpoint failure and database outage?
- From: Stuart Bishop <stuart(at)stuartbishop(dot)net>
- To: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
- Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
- Subject: Re: Re: [GENERAL] pgstattuple triggered checkpoint failure and database outage?
- Date: Tue, 31 Mar 2009 16:17:10 +0700
- Message-id: <6bc73d4c0903310217v551acfffqf225b8e51bda1e76@mail.gmail.com> <text/plain>
On Tue, Mar 31, 2009 at 2:20 PM, Heikki Linnakangas
<heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
>> This is exactly what happened, and temporary tables belonging to other
>> sessions where fed to pgstattuple.
>
> +1 for throwing an error. That's what we do for views, composite types, and
> GIN indexes as well. If you want to write a query to call pgstattuple for
> all tables in pg_class, you'll need to exclude all those cases anyway. To
> exclude temp tables of other sessions, you'll need to add "AND
> pg_is_other_temp_schema(relnamespace)".
I would have expected an exception to be raised personally.
> I'm ok with returning NULLs as well, but returning zeroes doesn't feel
> right.
--
Stuart Bishop <stuart(at)stuartbishop(dot)net>
http://www.stuartbishop.net/
Home |
Main Index |
Thread Index