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

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

From: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
To: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Re: [COMMITTERS] pgsql: Write a WAL record whenever we perform an operation without
Date: 2010-02-01 10:27:15
Message-ID: 4B66AC83.4070703@enterprisedb.com (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-hackers
Fujii Masao wrote:
> The cause of the problem seems to be the new heap created by
> rebuild_relation() and copy_heap_data(), i.e., new VACUUM FULL.
> Since it's not a temporary heap, its rd_istemp is off. OTOH
> it needs to be synced after physical copy from old heap.

Why does it need to be synced?

ISTM the bug is that rd_istemp is off at that point.

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

In response to

Responses

pgsql-hackers by date

Next:From: Heikki LinnakangasDate: 2010-02-01 10:30:43
Subject: Re: [COMMITTERS] pgsql: Write a WAL record whenever we perform an operation without
Previous:From: Fujii MasaoDate: 2010-02-01 10:15:21
Subject: Re: Re: [COMMITTERS] pgsql: Write a WAL record whenever we perform an operation without

pgsql-committers by date

Next:From: Heikki LinnakangasDate: 2010-02-01 10:30:43
Subject: Re: [COMMITTERS] pgsql: Write a WAL record whenever we perform an operation without
Previous:From: Fujii MasaoDate: 2010-02-01 10:15:21
Subject: Re: Re: [COMMITTERS] pgsql: Write a WAL record whenever we perform an operation without

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