From: | "Simon Riggs" <simon(at)2ndquadrant(dot)com> |
---|---|
To: | "Bruce Momjian" <bruce(at)momjian(dot)us> |
Cc: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Interaction of PITR backups andBulkoperationsavoiding WAL |
Date: | 2007-04-27 08:03:58 |
Message-ID: | 1177661038.3715.68.camel@silverbirch.site |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, 2007-04-26 at 18:51 -0400, Bruce Momjian wrote:
> 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.
>
> Simon, has this patch been submitted?
Yes
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2007-04-27 08:05:38 | Re: [PATCHES] Reviewers Guide to DeferredTransactions/TransactionGuarantee |
Previous Message | Dave Page | 2007-04-27 07:57:06 | Re: [Fwd: PGBuildfarm member narwhal Branch HEAD Status changed from OK to InstallCheck failure] |