Re: WAL bypass for CTAS

From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: Neil Conway <neilc(at)samurai(dot)com>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, pgsql-patches(at)postgresql(dot)org, Alon Goldshuv <agoldshuv(at)greenplum(dot)com>
Subject: Re: WAL bypass for CTAS
Date: 2005-06-05 08:06:37
Message-ID: 1117958797.3844.1257.camel@localhost.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

On Sun, 2005-06-05 at 10:20 +1000, Neil Conway wrote:
> Bruce Momjian wrote:
> > Could we do your NOLOGGING automatically in COPY if we test to see if
> > anyone else is connected to our current database?

Remember that this patch doe NOT yet handle COPY, but that is planned...

> That seems pretty fragile -- what happens if someone connects after the
> COPY has started? Considering that many COPY operations can take many
> minutes or hours, I don't think it is wise to make assumptions based on
> the initial state of the system.

Agreed.

Best Regards, Simon Riggs

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Gevik babakhani 2005-06-05 10:35:32 Re: Solution proposal for TODO item "Clients: sequences"
Previous Message Dennis Bjorklund 2005-06-05 06:00:04 Re: lastval()

Browse pgsql-patches by date

  From Date Subject
Next Message Andreas Pflug 2005-06-05 09:56:08 Re: Server instrumentation: pg_terminate_backend, pg_reload_conf
Previous Message Dennis Bjorklund 2005-06-05 06:00:04 Re: lastval()