Re: [COMMITTERS] pgsql: Write a WAL record whenever we perform an operation without

From: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
To: Simon Riggs <simon(at)2ndQuadrant(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [COMMITTERS] pgsql: Write a WAL record whenever we perform an operation without
Date: 2010-02-01 10:30:43
Message-ID: 4B66AD53.7030807@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Simon Riggs wrote:
> On Mon, 2010-02-01 at 12:11 +0200, Heikki Linnakangas wrote:
>> Simon Riggs wrote:
>>> On Mon, 2010-02-01 at 11:33 +0200, Heikki Linnakangas wrote:
>>>> Can you reproduce that?
>>> Every time
>> Ok, good :-). What I really meant was: How?
>
> As mentioned in first post: VACUUM FULL and CLUSTER.

I'm asking because I couldn't reproduce it. I added an elog(LOG) to
XLogReportUnloggedStatement() so that I can see when an unlogged-record
is written. Then I ran:

CREATE TEMPORARY TABLE foo (id int4);
VACUUM FULL foo;

But XLogReportUnloggedStatement() was not executed. When I removed the
"TEMPORARY" and tried again, it was executed.

--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Fujii Masao 2010-02-01 10:36:59 Re: Re: [COMMITTERS] pgsql: Write a WAL record whenever we perform an operation without
Previous Message Heikki Linnakangas 2010-02-01 10:27:15 Re: Re: [COMMITTERS] pgsql: Write a WAL record whenever we perform an operation without

Browse pgsql-hackers by date

  From Date Subject
Next Message Rafael Martinez 2010-02-01 10:33:56 PITR - Bug or feature?
Previous Message Heikki Linnakangas 2010-02-01 10:27:15 Re: Re: [COMMITTERS] pgsql: Write a WAL record whenever we perform an operation without