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

From Simon Riggs
Subject Re: [COMMITTERS] pgsql: Write a WAL record whenever we perform an operation without
Date
Msg-id 1265021166.13782.11353.camel@ebony
Whole thread Raw
In response to Re: [COMMITTERS] pgsql: Write a WAL record whenever we perform an operation without  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
List pgsql-hackers
On Mon, 2010-02-01 at 12:30 +0200, Heikki Linnakangas wrote:
> 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.

drop table if exists foo;
create table foo (col1 serial, col2 text);
insert into foo (col2) 
select repeat('a', 5000) from generate_series(1,1000);
create index on foo (col1);
cluster foo using foo_col1_idx;

So it appears this relates to toast tables.

-- Simon Riggs           www.2ndQuadrant.com



pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: [COMMITTERS] pgsql: Write a WAL record whenever we perform an operation without
Next
From: Tim Bunce
Date:
Subject: Re: Package namespace and Safe init cleanup for plperl UPDATE 3 [PATCH]