Re: Re: [GENERAL] pgstattuple triggered checkpoint failure and database outage? - Mailing list pgsql-hackers

From Stuart Bishop
Subject Re: Re: [GENERAL] pgstattuple triggered checkpoint failure and database outage?
Date
Msg-id 6bc73d4c0903310217v551acfffqf225b8e51bda1e76@mail.gmail.com
Whole thread Raw
In response to Re: Re: [GENERAL] pgstattuple triggered checkpoint failure and database outage?  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
List pgsql-hackers
On Tue, Mar 31, 2009 at 2:20 PM, Heikki Linnakangas
<heikki.linnakangas@enterprisedb.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@stuartbishop.net>
http://www.stuartbishop.net/


pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Re: [GENERAL] pgstattuple triggered checkpoint failure and database outage?
Next
From: Zdenek Kotala
Date:
Subject: Re: Solaris getopt_long and PostgreSQL