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

Re: [HACKERS] Re: pgsql: Extract catalog info for error reporting before an error actually

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: Michael Paesold <mpaesold(at)gmx(dot)at>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, pgsql-committers(at)postgresql(dot)org, Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [HACKERS] Re: pgsql: Extract catalog info for error reporting before an error actually
Date: 2007-10-25 19:54:28
Message-ID: 4720F474.9000401@dunslane.net (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-hackerspgsql-patches

Simon Riggs wrote:
> On Thu, 2007-10-25 at 13:51 -0400, Andrew Dunstan wrote:
>   
>> Michael Paesold wrote:
>>     
>>> In the previous discussion, Simon and me agreed that schema changes 
>>> should not happen on a regular basis on production systems.
>>>
>>> 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.
>>     
>
> We didn't agree that DDL was uncommon, we agreed that running DDL was
> more important than running an auto VACUUM. DDL runs very quickly,
> unless blocked, though holds up everybody else. So you must run it at
> pre-planned windows. VACUUMs can run at any time, so a autoVACUUM
> shouldn't be allowed to prevent DDL from running. The queuing DDL makes
> other requests queue behind it, even ones that would normally have been
> able to execute at same time as the VACUUM.
>
> Anyway, we covered all this before. I started off saying we shouldn't do
> this and Heikki and Michael came up with convincing arguments, for me,
> so now I think we should allow autovacuums to be cancelled.
>
>   

Perhaps I misunderstood, or have been mistunderstood :-) - I am actually 
agreeing that autovac should not block DDL.

cheers

andrew

In response to

Responses

pgsql-hackers by date

Next:From: Alvaro HerreraDate: 2007-10-25 20:07:41
Subject: Autovacuum cancellation
Previous:From: Bruce MomjianDate: 2007-10-25 19:44:49
Subject: Re: Re: [COMMITTERS] pgsql: Extract catalog info for error reporting before an error actually

pgsql-committers by date

Next:From: Alvaro HerreraDate: 2007-10-25 20:07:41
Subject: Autovacuum cancellation
Previous:From: Bruce MomjianDate: 2007-10-25 19:44:49
Subject: Re: Re: [COMMITTERS] pgsql: Extract catalog info for error reporting before an error actually

pgsql-patches by date

Next:From: Alvaro HerreraDate: 2007-10-25 20:07:41
Subject: Autovacuum cancellation
Previous:From: Bruce MomjianDate: 2007-10-25 19:44:49
Subject: Re: Re: [COMMITTERS] pgsql: Extract catalog info for error reporting before an error actually

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