Re: [GSoC2014] Patch ALTER TABLE ... SET LOGGED - Mailing list pgsql-hackers

From Christian Ullrich
Subject Re: [GSoC2014] Patch ALTER TABLE ... SET LOGGED
Date
Msg-id m4b32a$817$1@ger.gmane.org
Whole thread Raw
In response to Re: [GSoC2014] Patch ALTER TABLE ... SET LOGGED  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: [GSoC2014] Patch ALTER TABLE ... SET LOGGED  (Michael Paquier <michael.paquier@gmail.com>)
List 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






pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: Order of views in stats docs
Next
From: Steve Singer
Date:
Subject: Re: logical decoding - reading a user catalog table