Re: COPY with no WAL, in certain circumstances

From: Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>
To: pgsql-patches(at)postgresql(dot)org
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, Simon Riggs <simon(at)2ndquadrant(dot)com>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
Subject: Re: COPY with no WAL, in certain circumstances
Date: 2007-01-06 23:23:46
Message-ID: 200701061823.47137.xzilla@users.sourceforge.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

On Saturday 06 January 2007 16:40, Bruce Momjian wrote:
> Simon Riggs wrote:
> > > > Or in other words, does this patch mean that all COPY execution that
> > > > is within a transaction will ignore WAL?
> > >
> > > Yes, because it is possible to do in all cases.
> >
> > Very happy to add documentation where Tom suggested.
> >
> > Reason for no documentation was that CREATE INDEX and CREATE TABLE AS
> > SELECT already use this optimisation, but to my knowledge neither was/is
> > documented on those command pages.
>
> I wasn't aware those used the optimization. Seems they all should be
> documented somewhere.

Might I suggest somewhere under chapter 27, with something akin to what we
have for documenting lock levels and the different operations that use them.
We document the reasons you want to avoid WAL and various operations in the
database that do this automagically.

--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Treat 2007-01-06 23:29:36 Re: COPY with no WAL, in certain circumstances
Previous Message Peter Eisentraut 2007-01-06 23:13:29 Re: [HACKERS] Allow the identifier length to be increased via a configure option

Browse pgsql-patches by date

  From Date Subject
Next Message Robert Treat 2007-01-06 23:29:36 Re: COPY with no WAL, in certain circumstances
Previous Message Peter Eisentraut 2007-01-06 23:13:29 Re: [HACKERS] Allow the identifier length to be increased via a configure option