From: Simon Riggs <simon@2ndquadrant.com>
To: Jim C. Nasby <jnasby@pervasive.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: WAL logging of SELECT ... INTO command
Date: Wed, 22 Mar 2006 13:08:34 +0000
Message-ID: <1143032914.24487.632.camel@localhost.localdomain> (raw)
In-Reply-To: <20060322124732.GA15742@pervasive.com>
References: <20060321122211.GU15742@pervasive.com>
<1142973230.24487.501.camel@localhost.localdomain>
<20060322124732.GA15742@pervasive.com>
On Wed, 2006-03-22 at 06:47 -0600, Jim C. Nasby wrote:
> Also, why do we log rows for CTAS/SELECT INTO when PITR is in use for
> simple SELECTs (ones that don't call non-deterministic functions)? The
> data should alread be available AFAICS...
Not sure what you're asking... SELECTs don't produce WAL.
PITR wants all changes. Without PITR we can optimise certain logging
actions.
Best Regards, Simon Riggs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: simon@2ndquadrant.com, jnasby@pervasive.com
Subject: Re: WAL logging of SELECT ... INTO command
In-Reply-To: <1143032914.24487.632.camel@localhost.localdomain>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox