Re: TODO item: adding VERBOSE option to CLUSTER [with patch] - Mailing list pgsql-hackers

From Kevin Grittner
Subject Re: TODO item: adding VERBOSE option to CLUSTER [with patch]
Date
Msg-id 48F36A6C.EE98.0025.0@wicourts.gov
Whole thread Raw
In response to Re: TODO item: adding VERBOSE option to CLUSTER [with patch]  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: TODO item: adding VERBOSE option to CLUSTER [with patch]
List pgsql-hackers
>>> Tom Lane <tgl@sss.pgh.pa.us> wrote: 
> Gregory Stark <stark@enterprisedb.com> writes:
>> Tom Lane <tgl@sss.pgh.pa.us> writes:
>>> Short of actually running an ANALYZE, I'm not seeing a good way to
>>> derive the same number it derives.
> 
>> Well we could print the _old_ value at least.
> 
> +1 ... seems an appropriate amount of effort for the likely value.
That seems fine for sortedness, but am I the only one who would like
the verbose mode to show the bloat reduction?  Essentially, an INFO
line to show the same information you could get by bracketing the
CLUSTER with a couple SELECTs:
ccdev=# select pg_total_relation_size('"DbTranImageStatus"');pg_total_relation_size
------------------------                253952
(1 row)

ccdev=# cluster "DbTranImageStatus";
CLUSTER
ccdev=# select pg_total_relation_size('"DbTranImageStatus"');pg_total_relation_size
------------------------                 32768
(1 row)
-Kevin


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: TODO item: adding VERBOSE option to CLUSTER [with patch]
Next
From: Kris Jurka
Date:
Subject: Re: There's some sort of race condition with the new FSM stuff