Re: WAL logging of SELECT ... INTO command

From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: WAL logging of SELECT ... INTO command
Date: 2006-03-22 13:08:34
Message-ID: 1143032914.24487.632.camel@localhost.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches pgsql-performance

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

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Jim C. Nasby 2006-03-22 13:19:10 Re: WAL logging of SELECT ... INTO command
Previous Message Jim C. Nasby 2006-03-22 12:47:32 Re: WAL logging of SELECT ... INTO command

Browse pgsql-performance by date

  From Date Subject
Next Message Mikael Carneholm 2006-03-22 13:12:43 Re: Migration study, step 1: bulk write performanceoptimization
Previous Message Jim C. Nasby 2006-03-22 12:55:17 Re: Migration study, step 1: bulk write performanceoptimization