Patch applied. Thanks.
---
Simon Riggs wrote:
> VERSION 2, with all changed made as requested to date.
>
> As discussed on -hackers, its possible to avoid writing any WAL at all
> for COPY in these circumstances:
>
> htt
Patch applied. Thanks.
---
Simon Riggs wrote:
> On Fri, 2007-01-19 at 11:36 -0500, Bruce Momjian wrote:
> > Simon Riggs wrote:
> > >
> > > psql -f copy_nowal_prep.sql postgres
> > > psql -f copy_nowal_test.sql postgre
On Fri, 2007-01-19 at 11:36 -0500, Bruce Momjian wrote:
> Simon Riggs wrote:
> >
> > psql -f copy_nowal_prep.sql postgres
> > psql -f copy_nowal_test.sql postgres
> >
> > Do we want an additional test case along these lines?
> >
> > Agreed doc changes for Performance Tips forthcoming.
>
Simon Riggs wrote:
>
> psql -f copy_nowal_prep.sql postgres
> psql -f copy_nowal_test.sql postgres
>
> Do we want an additional test case along these lines?
>
> Agreed doc changes for Performance Tips forthcoming.
I am still waiting for the documentation patch.
--
Bruce Momjian
Will hold for doc patches.
Your patch has been added to the PostgreSQL unapplied patches list at:
http://momjian.postgresql.org/cgi-bin/pgpatches
It will be applied as soon as one of the PostgreSQL committers reviews
and approves it.
VERSION 2, with all changed made as requested to date.
As discussed on -hackers, its possible to avoid writing any WAL at all
for COPY in these circumstances:
http://archives.postgresql.org/pgsql-hackers/2006-10/msg01172.php
and again recently.
BEGIN;
CREATE TABLE foo..
COPY foo...
COMMIT;