On Thu, Oct 25, 2007 at 03:54:28PM -0400, Andrew Dunstan wrote:
> 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
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 in
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
Alvaro Herrera wrote:
Michael Paesold wrote:
Simon Riggs wrote:
On Thu, 2007-10-25 at 13:41 -0300, Alvaro Herrera wrote:
...
FWIW I disagree with cancelling just any autovac work automatically; in
my patch I'm only cancelling if it's analyze, on the grounds that if
you have really bad luck yo
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
shou
Michael Paesold wrote:
> Simon Riggs wrote:
>> On Thu, 2007-10-25 at 13:41 -0300, Alvaro Herrera wrote:
> ...
>>> FWIW I disagree with cancelling just any autovac work automatically; in
>>> my patch I'm only cancelling if it's analyze, on the grounds that if
>>> you have really bad luck you can pot
Simon Riggs wrote:
On Thu, 2007-10-25 at 13:41 -0300, Alvaro Herrera wrote:
...
FWIW I disagree with cancelling just any autovac work automatically; in
my patch I'm only cancelling if it's analyze, on the grounds that if
you have really bad luck you can potentially lose a lot of work that
vacuu
On Thu, 2007-10-25 at 13:41 -0300, Alvaro Herrera wrote:
> Simon Riggs wrote:
> > On Thu, 2007-10-25 at 14:45 +, Alvaro Herrera wrote:
> > > Log Message:
> > > ---
> > > Extract catalog info for error reporting before an error actually happens.
> > > Also, remove redundant reset of for-
Simon Riggs wrote:
> On Thu, 2007-10-25 at 14:45 +, Alvaro Herrera wrote:
> > Log Message:
> > ---
> > Extract catalog info for error reporting before an error actually happens.
> > Also, remove redundant reset of for-wraparound PGPROC flag.
>
> Just noticed you've made these changes.
On Thu, 2007-10-25 at 14:45 +, Alvaro Herrera wrote:
> Log Message:
> ---
> Extract catalog info for error reporting before an error actually happens.
> Also, remove redundant reset of for-wraparound PGPROC flag.
Just noticed you've made these changes. I was working on them, but
hadn't
Log Message:
---
Extract catalog info for error reporting before an error actually happens.
Also, remove redundant reset of for-wraparound PGPROC flag.
Thanks to Tom Lane for noticing both bogosities.
Modified Files:
--
pgsql/src/backend/postmaster:
autovacuum.c (r
11 matches
Mail list logo
