Skip site navigation (1) Skip section navigation (2)

Re: WAL logging of SELECT ... INTO command

From: "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>
To: Qingqing Zhou <zhouqq(at)cs(dot)toronto(dot)edu>, pgsql-performance(at)postgresql(dot)org
Subject: Re: WAL logging of SELECT ... INTO command
Date: 2006-03-24 13:01:21
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-patchespgsql-performance
On Fri, Mar 24, 2006 at 08:39:02AM -0400, Alvaro Herrera wrote:
> Jim C. Nasby wrote:
> > Why would the content of the old_table be unreliable? If we've replayed
> > logs up to the point of the CTAS then any data that would be visible to
> > the CTAS should be fine, no?
> > 
> > Though, the way Tom put it in one of his replies it sounds like WAL
> > doesn't do any kind of statement logging, only data logging. If that's
> > the case I'm not sure that the CTAS would actually get replayed. But I
> > suspect I'm just misunderstanding...
> The CTAS doesn't get logged (nor replayed obviously).  What happens is
> that the involved files are fsync'ed before transaction commit, AFAIR.

Ahh, yes, that sounds right. Might be a nice gain to be had if there was
some way to log the statement, but I suspect getting WAL to support that
would be extremely non-trivial.
Jim C. Nasby, Sr. Engineering Consultant      jnasby(at)pervasive(dot)com
Pervasive Software    work: 512-231-6117
vcard:       cell: 512-569-9461

In response to


pgsql-performance by date

Next:From: Ruben Rubio ReyDate: 2006-03-24 13:01:29
Subject: Re: Array performance
Previous:From: Jim C. NasbyDate: 2006-03-24 12:59:19
Subject: Re: Performance problems with multiple layers of functions

pgsql-patches by date

Next:From: Alvaro HerreraDate: 2006-03-24 13:47:20
Subject: Re: WAL logging of SELECT ... INTO command
Previous:From: Alvaro HerreraDate: 2006-03-24 12:39:02
Subject: Re: WAL logging of SELECT ... INTO command

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group