Re: pgsql: Implement ALTER TABLE .. SET LOGGED / UNLOGGED - Mailing list pgsql-committers

From Simon Riggs
Subject Re: pgsql: Implement ALTER TABLE .. SET LOGGED / UNLOGGED
Date
Msg-id CA+U5nMJJtjL7e5+CgsdNhgCyqR8vcfFZeQpvPs49oV5m7mnLvw@mail.gmail.com
Whole thread Raw
In response to Re: pgsql: Implement ALTER TABLE .. SET LOGGED / UNLOGGED  (Andres Freund <andres@anarazel.de>)
Responses Re: pgsql: Implement ALTER TABLE .. SET LOGGED / UNLOGGED
List pgsql-committers
On 23 August 2014 14:57, Andres Freund <andres@anarazel.de> wrote:
> On August 23, 2014 3:49:32 PM CEST, Simon Riggs <simon@2ndQuadrant.com> wrote:
>>On 22 August 2014 19:30, Alvaro Herrera <alvherre@alvh.no-ip.org>
>>wrote:
>>
>>> Implement ALTER TABLE .. SET LOGGED / UNLOGGED
>>>

>>When moving from unlogged to logged, where do we remove the init fork?
>>
>>Couldn't see the keywords fork or init anywhere in the patch, so maybe
>>its hidden somewhere.
>
> A new relfilenode is filled with the data - the old one, including the init fork, gets removed by the normal
mechanicsof rewriting rels. 

Why do we do that? Table rewrite takes hours.

If that is a requirement, I don't see it documented. If its a choice,
its a bad one.

--
 Simon Riggs                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services


pgsql-committers by date:

Previous
From: Andres Freund
Date:
Subject: Re: pgsql: Implement ALTER TABLE .. SET LOGGED / UNLOGGED
Next
From: Andres Freund
Date:
Subject: Re: pgsql: Implement ALTER TABLE .. SET LOGGED / UNLOGGED