Skip site navigation (1) Skip section navigation (2)

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: 2009-03-31 09:17:10
Message-ID: 6bc73d4c0903310217v551acfffqf225b8e51bda1e76@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-generalpgsql-hackers
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/

In response to

pgsql-hackers by date

Next:From: Zdenek KotalaDate: 2009-03-31 11:37:16
Subject: Re: Solaris getopt_long and PostgreSQL
Previous:From: Heikki LinnakangasDate: 2009-03-31 07:24:03
Subject: Re: [GENERAL] pgstattuple triggered checkpoint failure and database outage?

pgsql-general by date

Next:From: Chris.EllisDate: 2009-03-31 09:37:53
Subject: Server Performance
Previous:From: Richard HuxtonDate: 2009-03-31 08:34:57
Subject: Re: Schema for J2EE project

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group