Re: COPY LOCK for WAL bypass - Mailing list pgsql-patches

From Bruce Momjian
Subject Re: COPY LOCK for WAL bypass
Date
Msg-id 200512211920.jBLJKct29185@candle.pha.pa.us
Whole thread Raw
In response to Re: COPY LOCK for WAL bypass  (Simon Riggs <simon@2ndquadrant.com>)
List 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@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

pgsql-patches by date:

Previous
From: Simon Riggs
Date:
Subject: Re: COPY LOCK for WAL bypass
Next
From: Bruce Momjian
Date:
Subject: Re: [BUGS] BUG #2120: Crash when doing UTF8<->ISO_8859_8 encoding conversion