Re: WAL logging of SELECT ... INTO command - Mailing list pgsql-performance

From Alvaro Herrera
Subject Re: WAL logging of SELECT ... INTO command
Date
Msg-id 20060324123902.GA14217@surnet.cl
Whole thread Raw
In response to Re: WAL logging of SELECT ... INTO command  ("Jim C. Nasby" <jnasby@pervasive.com>)
Responses Re: WAL logging of SELECT ... INTO command
List pgsql-performance
Jim C. Nasby wrote:

> Why would the content of the old_table be unreliable? If we've replayed
> logs up to the point of the CTAS then any data that would be visible to
> the CTAS should be fine, no?
>
> Though, the way Tom put it in one of his replies it sounds like WAL
> doesn't do any kind of statement logging, only data logging. If that's
> the case I'm not sure that the CTAS would actually get replayed. But I
> suspect I'm just misunderstanding...

The CTAS doesn't get logged (nor replayed obviously).  What happens is
that the involved files are fsync'ed before transaction commit, AFAIR.

--
Alvaro Herrera                                http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

pgsql-performance by date:

Previous
From: "Jim C. Nasby"
Date:
Subject: Re: Problem with query, server totally unresponsive
Next
From: Ruben Rubio Rey
Date:
Subject: Array performance