Re: [HACKERS] Non-transactional pg_class, try 2

From: "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, pgsql-patches(at)postgresql(dot)org
Subject: Re: [HACKERS] Non-transactional pg_class, try 2
Date: 2006-06-29 21:37:41
Message-ID: 20060629213740.GP17241@pervasive.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

On Thu, Jun 29, 2006 at 09:39:27AM +0100, Simon Riggs wrote:
> On Wed, 2006-06-28 at 20:08 -0400, Tom Lane wrote:
> > In fact, maybe we should just force an autovac cycle for any DB that
> > appears to be approaching wraparound, rather than waiting for the
> > shutdown-before-wraparound code to kick in. Getting into that state
> > amounts to whacking DBAs upside the head for being stupid, which
> > doesn't really win us any friends ...
>
> Yes, please can we have the auto autovacuum cut in rather than the
> wraparound message? I'd rather have them complain that we did this, than
> complain that we didn't.
>
> Normally, I wouldn't support automatically starting admin tasks without
> thr sysadmins knowledge.

I think it'd be good to put a big, fat WARNING in the log if we fire up
an autovac to avoid an XID wrap, since it's an indication that the
vacuuming scheme that's in place probably isn't good enough.
--
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

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Hannu Krosing 2006-06-29 21:37:53 Re: Index corruption
Previous Message Hannu Krosing 2006-06-29 21:23:45 Re: Index corruption

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2006-06-29 22:01:08 Re: [HACKERS] Non-transactional pg_class, try 2
Previous Message Alvaro Herrera 2006-06-29 20:37:36 Re: [HACKERS] Non-transactional pg_class, try 2