Re: Interaction of PITR backups and Bulkoperationsavoiding WAL

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: "Jim C(dot) Nasby" <decibel(at)decibel(dot)org>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, 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-05-16 00:47:35
Message-ID: 200705160047.l4G0lZm15515@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


OK, removed.

---------------------------------------------------------------------------

Jim C. Nasby wrote:
> Simon intended to commit this per
> http://archives.postgresql.org/pgsql-hackers/2007-03/msg01761.php
> (actually, there was a change in what was being done). I suspect this
> item isn't valid any longer.
>
> On Tue, May 15, 2007 at 07:30:58PM -0400, Bruce Momjian wrote:
> >
> > This has been saved for the 8.4 release:
> >
> > http://momjian.postgresql.org/cgi-bin/pgpatches_hold
> >
> > ---------------------------------------------------------------------------
> >
> > 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 Riggs
> > > EnterpriseDB http://www.enterprisedb.com
> > >
> > >
> > >
> > > ---------------------------(end of broadcast)---------------------------
> > > TIP 6: explain analyze is your friend
> >
> > --
> > 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. +
> >
> > ---------------------------(end of broadcast)---------------------------
> > TIP 3: Have you checked our extensive FAQ?
> >
> > http://www.postgresql.org/docs/faq
> >
>
> --
> Jim Nasby decibel(at)decibel(dot)org
> EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)

--
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

Browse pgsql-hackers by date

  From Date Subject
Next Message Tatsuo Ishii 2007-05-16 01:16:43 Re: Not ready for 8.3
Previous Message Jim C. Nasby 2007-05-16 00:38:10 Re: Maintaining cluster order on insert