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

From Qingqing Zhou
Subject Re: WAL logging of SELECT ... INTO command
Date
Msg-id dvqqi5$1nmv$1@news.hub.org
Whole thread Raw
In response to WAL logging of SELECT ... INTO command  ("Jim C. Nasby" <jnasby@pervasive.com>)
Responses Re: WAL logging of SELECT ... INTO command  ("Jim C. Nasby" <jnasby@pervasive.com>)
List pgsql-performance
"Simon Riggs" <simon@2ndquadrant.com> wrote
> On Tue, 2006-03-21 at 06:22 -0600, Jim C. Nasby wrote:
> > Currently, it appears that SELECT * INTO new_table FROM old_table logs
> > each page as it's written to WAL. Is this actually needed? Couldn't the
> > database simply log that the SELECT ... INTO statement was executed
> > instead? Doing so would likely result in a large performance improvement
> > in most installs. Is there no provision for writing anything but data
> > page changes (or whole pages) to WAL?
>
> AFAIK it takes the same code path as CREATE TABLE AS SELECT, which
> already does exactly what you suggest (except when using PITR).
>

As I read, they did take the same code path, but did they "simply log that
the SELECT ... INTO statement was executed"? If so, how can we rely on the
unreliable content of the old_table to do recovery?

Regards,
Qingqing


pgsql-performance by date:

Previous
From: Kris Jurka
Date:
Subject: Re: WAL logging of SELECT ... INTO command
Next
From: "Jojo Paderes"
Date:
Subject: Scaling up PostgreSQL in Multiple CPU / Dual Core Powered Servers