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

From Simon Riggs
Subject Re: WAL logging of SELECT ... INTO command
Date
Msg-id 1142973230.24487.501.camel@localhost.localdomain
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
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).

Best Regards, Simon Riggs


pgsql-performance by date:

Previous
From: Vivek Khera
Date:
Subject: Re: Best OS & Configuration for Dual Xeon w/4GB & Adaptec
Next
From: Simon Riggs
Date:
Subject: Re: Migration study, step 1: bulk write performance