Re: Re: [COMMITTERS] pgsql: Extract catalog info for error reporting before an error actually - Mailing list pgsql-hackers

From Stefan Kaltenbrunner
Subject Re: Re: [COMMITTERS] pgsql: Extract catalog info for error reporting before an error actually
Date
Msg-id 4720FC86.3030501@kaltenbrunner.cc
Whole thread Raw
In response to Re: Re: [COMMITTERS] pgsql: Extract catalog info for error reporting before an error actually  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane wrote:
> Andrew Dunstan <andrew@dunslane.net> writes:
>> Michael Paesold wrote:
>>> Shouldn't we rather support the regular usage pattern instead of the 
>>> uncommon one? Users doing a lot of schema changes are the ones who 
>>> should have to work around issues, not those using a DBMS sanely. No?
> 
>> Unfortunately, doing lots of schema changes is a very common phenomenon. 
>> It makes me uncomfortable too, but saying that those who do it have to 
>> work around issues isn't acceptable IMNSHO - it's far too widely done.
> 
> Well, there's going to be pain *somewhere* here, and we already know
> that users will find the current 8.3 behavior unacceptable.  I'd rather
> have autovacuum not make progress than have users turn it off because it
> gets in their way too much.  Which I think is exactly what will happen
> if we ship it with the current behavior.

exactly - 8.3 will be the first release with autovac enabled by default
(and concurrent autovacuuming) and we really need to make sure that
people wont get surprised by it in the way I (and others) did when
playing with Beta1.
So my vote would be on cancelling always except in the case of a
wraparound vacuum.

Stefan


pgsql-hackers by date:

Previous
From: "Jignesh K. Shah"
Date:
Subject: 8.3beta1 testing on Solaris
Next
From: Tom Lane
Date:
Subject: Re: 8.3beta1 testing on Solaris