Re: COPY LOCK for WAL bypass

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>, Chris Browne <cbbrowne(at)acm(dot)org>, pgsql-patches(at)postgresql(dot)org
Subject: Re: COPY LOCK for WAL bypass
Date: 2005-12-21 19:20:38
Message-ID: 200512211920.jBLJKct29185@candle.pha.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-patches

Simon Riggs wrote:
> > Right, just disable with a clear error message.
> >
>
> Forgive me if my earlier reply was not clear: This patch works just the
> same way CREATE INDEX and CREATE TABLE AS SELECT already works:
> - if the server has archive_command set, WAL is written
> - if archive_command is not set then (assuming other conditions apply)
> the writing WAL will be bypassed for performance.
> There is no error-message generated, by COPY LOCK nor the other two
> previously mentioned commands.

Sounds good.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Browse pgsql-patches by date

  From Date Subject
Next Message Hannu Krosing 2005-12-21 23:12:19 Re: status of concurrent VACUUM patch ...
Previous Message Simon Riggs 2005-12-21 17:15:19 Re: COPY LOCK for WAL bypass