Skip site navigation (1) Skip section navigation (2)

Re: COPY LOCK for WAL bypass

From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: Chris Browne <cbbrowne(at)acm(dot)org>
Cc: pgsql-patches(at)postgresql(dot)org
Subject: Re: COPY LOCK for WAL bypass
Date: 2005-12-19 07:51:54
Message-ID: 1134978714.2964.232.camel@localhost.localdomain (view raw, whole thread or download thread mbox)
Lists: pgsql-patches
On Sun, 2005-12-18 at 22:03 -0500, Chris Browne wrote:
> simon(at)2ndquadrant(dot)com (Simon Riggs) writes:
> > On Sat, 2005-12-10 at 12:07 +0000, Simon Riggs wrote:
> >> Following patch implements COPY ... FROM ... LOCK
> >
> > Patch now updated so that it includes an additional optimization of
> > COPY, so that WAL will not be written in the transaction that created
> > the table.
> >
> > This now gives two fast paths for COPY:
> > 1) COPY LOCK
> > 2) COPY in same transaction (e.g. reloading a pg_dump)
> I presume that if this doesn't go into WAL, that means that this kind
> of update wouldn't play with PITR, right?

You're right.

PITR is designed for normal production use, rather than initial loading.
It is also fairly common to turn PITR off permanently in larger data
warehouses, which is also where these optimizations are aimed.

I'll take the hint and write the docs then. :-)

Best Regards, Simon Riggs

In response to


pgsql-patches by date

Next:From: Serge A. RibalchenkoDate: 2005-12-19 16:45:27
Subject: new uk_UA i18n file
Previous:From: Chris BrowneDate: 2005-12-19 03:03:40
Subject: Re: COPY LOCK for WAL bypass

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group