pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Simon@2ndquadrant.com <simon@2ndquadrant.com>
To: Bruce Momjian <pgman@candle.pha.pa.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Klaus Naumann <kn@mgnet.de>
Cc: markw@osdl.org
Cc: pgsql-patches@postgresql.org
Subject: Re: [HACKERS] Point in Time Recovery
Date: Sat, 14 Aug 2004 01:50:22 +0100
Message-ID: <NOEFLCFHBPDAFHEIPGBOCEHDCCAA.simon@2ndquadrant.com> (raw)
In-Reply-To: <200407291733.i6THXZP20332@candle.pha.pa.us>


> Tom Lane wrote:
> > Bruce Momjian <pgman@candle.pha.pa.us> writes:
> > > Now, if you say people will rarely turn archiving on/off, then one
> > > parameter seems to make more sense.
> >
> > I really can't envision a situation where people would do that.  If you
> > need PITR at all then you need it 24x7.
>
I agree. The second parameter is only there to clarify the intent.

8.0 does introduce two good reasons to turn it on/off, however:
- index build speedups
- COPY speedups

I would opt to make enabling/disabling archive_command require a postmaster
restart. That way there would be no capability to take advantage of the
incentive to turn it on/off.

For TODO:

It would be my intention (in 8.1) to make those available via switches e.g.
NOT LOGGED options on CREATE INDEX and COPY, to allow users to take
advantage of the no logging optimization without turning off PITR system
wide. (Just as this is possible in Oracle and Teradata).

I would also aim to make the first Insert Select into an empty table not
logged (optionally). This is an important optimization for Oracle, teradata
and DB2 (which uses NOT LOGGED INITIALLY).

Best Regards, Simon Riggs




view thread (111+ messages)  latest in thread

Message-ID: <NOEFLCFHBPDAFHEIPGBOCEHDCCAA.simon@2ndquadrant.com>
Permalink:  ../NOEFLCFHBPDAFHEIPGBOCEHDCCAA.simon@2ndquadrant.com/
Also on:    postgresql.org/message-id/NOEFLCFHBPDAFHEIPGBOCEHDCCAA.simon@2ndquadrant.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: simon@2ndquadrant.com, pgman@candle.pha.pa.us, tgl@sss.pgh.pa.us, kn@mgnet.de, markw@osdl.org, pgsql-patches@postgresql.org
  Subject: Re: [HACKERS] Point in Time Recovery
  In-Reply-To: <NOEFLCFHBPDAFHEIPGBOCEHDCCAA.simon@2ndquadrant.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox