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

Re: COPY LOCK for WAL bypass

From: Chris Browne <cbbrowne(at)acm(dot)org>
To: pgsql-patches(at)postgresql(dot)org
Subject: Re: COPY LOCK for WAL bypass
Date: 2005-12-19 03:03:40
Message-ID: (view raw or whole thread)
Lists: pgsql-patches
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:
> 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?

That's presumably something that otta be pretty carefully documented
select 'cbbrowne' || '@' || '';
Microsoft Outlook: Deploying Viruses Has Never Been This Easy!

In response to


pgsql-patches by date

Next:From: Simon RiggsDate: 2005-12-19 07:51:54
Subject: Re: COPY LOCK for WAL bypass
Previous:From: Tom LaneDate: 2005-12-19 03:03:27
Subject: Re: Single-Transaction Utility options

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