| 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 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2010-02-01 10:30:43 | Re: [COMMITTERS] pgsql: Write a WAL record whenever we perform an operation without |
| Previous Message | Fujii Masao | 2010-02-01 10:15:21 | Re: Re: [COMMITTERS] pgsql: Write a WAL record whenever we perform an operation without |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2010-02-01 10:30:43 | Re: [COMMITTERS] pgsql: Write a WAL record whenever we perform an operation without |
| Previous Message | Fujii Masao | 2010-02-01 10:15:21 | Re: Re: [COMMITTERS] pgsql: Write a WAL record whenever we perform an operation without |