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
pgsql-hackers by date
| Next: | From: Rafael Martinez | Date: 2010-02-01 10:33:56 |
| Subject: PITR - Bug or feature? |
| Previous: | From: Heikki Linnakangas | Date: 2010-02-01 10:27:15 |
| Subject: Re: Re: [COMMITTERS] pgsql: Write a WAL record whenever
we perform an operation without |
pgsql-committers by date
| Next: | From: Fujii Masao | Date: 2010-02-01 10:36:59 |
| Subject: Re: Re: [COMMITTERS] pgsql: Write a WAL record whenever we perform an operation without |
| Previous: | From: Heikki Linnakangas | Date: 2010-02-01 10:27:15 |
| Subject: Re: Re: [COMMITTERS] pgsql: Write a WAL record whenever
we perform an operation without |