Simon Riggs wrote:
On Sun, 2005-12-18 at 22:03 -0500, Chris Browne wrote:
[EMAIL PROTECTED] (Simon Riggs) writes:
On Sat, 2005-12-10 at 12:07 +, Simon Riggs wrote:
Following patch implements COPY ... FROM ... LOCK
Patch now updated so that it includes an additional optimization
Jim C. Nasby wrote:
On Mon, Dec 19, 2005 at 07:51:54AM +, Simon Riggs wrote:
On Sun, 2005-12-18 at 22:03 -0500, Chris Browne wrote:
[EMAIL PROTECTED] (Simon Riggs) writes:
On Sat, 2005-12-10 at 12:07 +, Simon Riggs wrote:
Following patch implements COPY ... FROM ... LOCK
On Wed, 2005-12-21 at 08:18 -0500, Bruce Momjian wrote:
Jim C. Nasby wrote:
On Mon, Dec 19, 2005 at 07:51:54AM +, Simon Riggs wrote:
On Sun, 2005-12-18 at 22:03 -0500, Chris Browne wrote:
[EMAIL PROTECTED] (Simon Riggs) writes:
On Sat, 2005-12-10 at 12:07 +, Simon Riggs
On Wed, 2005-12-21 at 16:23 +, Simon Riggs wrote:
Writing docs now.
Here's the docs...
Hopefully that explains everything a little betterbut this doc patch
contains a ref to the as yet unapplied --single-transaction patch, but
also explains why that patch exists also.
[Patch via
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
On Mon, Dec 19, 2005 at 07:51:54AM +, Simon Riggs wrote:
On Sun, 2005-12-18 at 22:03 -0500, Chris Browne wrote:
[EMAIL PROTECTED] (Simon Riggs) writes:
On Sat, 2005-12-10 at 12:07 +, Simon Riggs wrote:
Following patch implements COPY ... FROM ... LOCK
Patch now updated so
On Sun, 2005-12-18 at 22:03 -0500, Chris Browne wrote:
[EMAIL PROTECTED] (Simon Riggs) writes:
On Sat, 2005-12-10 at 12:07 +, Simon Riggs wrote:
Following patch implements COPY ... FROM ... LOCK
Patch now updated so that it includes an additional optimization of
COPY, so that WAL
On Sat, 2005-12-10 at 12:07 +, 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)
[EMAIL PROTECTED] (Simon Riggs) writes:
On Sat, 2005-12-10 at 12:07 +, 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.
Following patch implements COPY ... FROM ... LOCK as discussed earlier
this year on these threads:
http://archives.postgresql.org/pgsql-hackers/2005-06/msg00069.php
http://archives.postgresql.org/pgsql-hackers/2005-06/msg00075.php
The purpose of the new command is to make an explicit request to
10 matches
Mail list logo