Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: WAL logging of SELECT ... INTO command
- From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
- To: "Jim C. Nasby" <jnasby(at)pervasive(dot)com>
- Cc: Qingqing Zhou <zhouqq(at)cs(dot)toronto(dot)edu>, pgsql-performance(at)postgresql(dot)org
- Subject: Re: WAL logging of SELECT ... INTO command
- Date: Fri, 24 Mar 2006 08:39:02 -0400
- Message-id: <20060324123902(dot)GA14217(at)surnet(dot)cl>
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. -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support
- Follow-Ups:
- Re: WAL logging of SELECT ... INTO command
- From: Jim C. Nasby
- Re: WAL logging of SELECT ... INTO command
- References:
- WAL logging of SELECT ... INTO command
- From: Jim C. Nasby
- Re: WAL logging of SELECT ... INTO command
- From: Simon Riggs
- Re: WAL logging of SELECT ... INTO command
- From: Qingqing Zhou
- Re: WAL logging of SELECT ... INTO command
- From: Jim C. Nasby
- WAL logging of SELECT ... INTO command
- Prev by Date: Re: Problem with query, server totally unresponsive
- Next by Date: Array performance
- Previous by thread: Re: WAL logging of SELECT ... INTO command
- Next by thread: Re: WAL logging of SELECT ... INTO command
- Indexes: