Re: WAL logging of SELECT ... INTO command

From: Simon Riggs
Subject: Re: WAL logging of SELECT ... INTO command
Date: ,
Msg-id: 1143032914.24487.632.camel@localhost.localdomain
(view: Whole thread, Raw)
In response to: Re: WAL logging of SELECT ... INTO command  ("Jim C. Nasby")
Responses: Re: WAL logging of SELECT ... INTO command  ("Jim C. Nasby")
List: pgsql-performance

Tree view

WAL logging of SELECT ... INTO command  ("Jim C. Nasby", )
 Re: WAL logging of SELECT ... INTO command  (Simon Riggs, )
  Re: WAL logging of SELECT ... INTO command  ("Jim C. Nasby", )
   Re: WAL logging of SELECT ... INTO command  (Simon Riggs, )
    Re: WAL logging of SELECT ... INTO command  ("Jim C. Nasby", )
     Re: WAL logging of SELECT ... INTO command  (Tom Lane, )
      Re: WAL logging of SELECT ... INTO command  ("Jim C. Nasby", )
       Re: WAL logging of SELECT ... INTO command  (Tom Lane, )
        Re: WAL logging of SELECT ... INTO command  (Csaba Nagy, )
   Re: WAL logging of SELECT ... INTO command  (Kris Jurka, )
    Re: WAL logging of SELECT ... INTO command  ("Jim C. Nasby", )
     Re: WAL logging of SELECT ... INTO command  (Kris Jurka, )
      Re: WAL logging of SELECT ... INTO command  (Bruce Momjian, )
       Re: WAL logging of SELECT ... INTO command  (Simon Riggs, )
      Re: WAL logging of SELECT ... INTO command  (Bruce Momjian, )
 Re: WAL logging of SELECT ... INTO command  ("Qingqing Zhou", )
  Re: WAL logging of SELECT ... INTO command  ("Jim C. Nasby", )
   Re: WAL logging of SELECT ... INTO command  (Alvaro Herrera, )
    Re: WAL logging of SELECT ... INTO command  ("Jim C. Nasby", )
     Re: WAL logging of SELECT ... INTO command  (Alvaro Herrera, )
      Re: WAL logging of SELECT ... INTO command  ("Jim C. Nasby", )

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



pgsql-performance by date:

From: "Luke Lonergan"
Date:
Subject: Re: Intel C/C++ Compiler Tests
From: Kris Jurka
Date:
Subject: Re: WAL logging of SELECT ... INTO command