| From: | Thomas Munro <munro(at)ip9(dot)org> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: CLUSTER FREEZE |
| Date: | 2013-10-25 22:19:02 |
| Message-ID: | CADLWmXVbAVZUhnHXdo4iT86_+E8QyKfTVdE9FVdgbh3d9cDAAw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 25 October 2013 01:17, Josh Berkus <josh(at)agliodbs(dot)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 | Content-Type | Size |
|---|---|---|
| cluster-freeze-always.patch | application/octet-stream | 1.2 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2013-10-26 02:07:44 | Re: logical changeset generation v6.4 |
| Previous Message | Heikki Linnakangas | 2013-10-25 19:13:17 | Re: Failure while inserting parent tuple to B-tree is not fun |