Re: CLUSTER FREEZE - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: CLUSTER FREEZE
Date
Msg-id CADLWmXVbAVZUhnHXdo4iT86_+E8QyKfTVdE9FVdgbh3d9cDAAw@mail.gmail.com
Whole thread Raw
In response to Re: CLUSTER FREEZE  (Josh Berkus <josh@agliodbs.com>)
Responses Re: CLUSTER FREEZE  (David Rowley <dgrowleyml@gmail.com>)
List pgsql-hackers
On 25 October 2013 01:17, Josh Berkus <josh@agliodbs.com> wrote:
On 10/24/2013 04:55 PM, Robert Haas wrote:
> I wonder if we should go so far as to make this the default behavior,
> instead of just making it an option.

+1 from me.  Can you think of a reason you *wouldn't* want to freeze?

Ok, I attach an alternative patch that makes CLUSTER *always* freeze, without any option (but doesn't affect VACUUM FULL in the same way). I will post both alternatives to the commitfest app since there seems to be some disagreement about whether tuple freezing should be an optional.

Thanks
Thomas Munro
Attachment

pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Failure while inserting parent tuple to B-tree is not fun
Next
From: Robert Haas
Date:
Subject: Re: logical changeset generation v6.4