| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Thomas Munro <munro(at)ip9(dot)org> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: CLUSTER FREEZE |
| Date: | 2013-10-24 17:09:00 |
| Message-ID: | 5269542C.5080509@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 10/23/2013 09:58 PM, Amit Kapila wrote:
> I wonder why anyone would like to freeze during CLUSTER command when
> they already have separate way (VACUUM FREEZE) to achieve it, do you
> know or can think of any case where user wants to do it along with
> Cluster command?
"If I'm rewriting the table anyway, let's freeze it".
Otherwise, you have to write the same pages twice, if both CLUSTER and
FREEZE are required.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2013-10-24 17:10:51 | Re: Add min and max execute statement time in pg_stat_statement |
| Previous Message | Andres Freund | 2013-10-24 17:00:28 | Re: [PATCH] Use MAP_HUGETLB where supported (v3) |