Re: Interaction of PITR backups and Bulkoperationsavoiding WAL

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Interaction of PITR backups and Bulkoperationsavoiding WAL
Date: 2007-04-05 02:05:10
Message-ID: 200704050205.l3525A020667@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Simon Riggs wrote:
> On Fri, 2007-03-09 at 11:47 -0500, Tom Lane wrote:
> > "Simon Riggs" <simon(at)2ndquadrant(dot)com> writes:
> > > On Fri, 2007-03-09 at 11:15 -0500, Tom Lane wrote:
> > >> It strikes me that allowing archive_command to be changed on the fly
> > >> might not be such a good idea though, or at least it shouldn't be
> > >> possible to flip it from empty to nonempty during live operation.
> >
> > > I'd rather fix it the proposed way than force a restart. ISTM wrong to
> > > have an availability feature cause downtime.
> >
> > I don't think that people are very likely to need to turn archiving on
> > and off on-the-fly. Your proposed solution introduces a great deal of
> > complexity (and risk of future bugs-of-omission, to say nothing of race
> > conditions) to solve a non-problem. We have better things to be doing
> > with our development time.
>
> It's certainly a quicker fix. Unless others object, I'll set
> archive_command to only be changeable at server startup.

I _still_ have no patch for this.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2007-04-05 02:10:38 Re: Optimized pgbench for 8.3
Previous Message Bruce Momjian 2007-04-05 02:04:27 Re: Modifying TOAST thresholds