Re: [GSoC2014] Patch ALTER TABLE ... SET LOGGED

From: Christian Ullrich <chris(at)chrullrich(dot)net>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [GSoC2014] Patch ALTER TABLE ... SET LOGGED
Date: 2014-11-16 20:56:41
Message-ID: m4b32a$817$1@ger.gmane.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

* Alvaro Herrera wrote:

> Michael Paquier wrote:
>
>> Btw, perhaps this diff should be pushed as a different patch as this is a
>> rather different thing:
>> - if (heapRelation->rd_rel->relpersistence == RELPERSISTENCE_UNLOGGED
>> &&
>> + if (indexRelation->rd_rel->relpersistence ==
>> RELPERSISTENCE_UNLOGGED &&
>> !smgrexists(indexRelation->rd_smgr, INIT_FORKNUM)
>> As this is a correctness fix, it does not seem necessary to back-patch it:
>> the parent relation always has the same persistence as its indexes.
>
> There was an argument for doing it this way that only applies if this
> patch went in, but I can't remember now what it was.
>
> Anyway I pushed the patch after some slight additional changes. Thanks!

The buildfarm says -DCLOBBER_CACHE_ALWAYS does not like this patch.

--
Christian

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Steve Singer 2014-11-16 21:49:27 Re: logical decoding - reading a user catalog table
Previous Message Magnus Hagander 2014-11-16 14:43:17 Re: Order of views in stats docs