From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
Cc: | ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>, Bruce Momjian <bruce(at)momjian(dot)us>, pgsql-patches(at)postgresql(dot)org, ishii(at)sraoss(dot)co(dot)jp |
Subject: | Re: pgstattuple extension for indexes |
Date: | 2006-07-24 14:52:49 |
Message-ID: | 10827.1153752769@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> ITAGAKI Takahiro wrote:
>> BTW, should we change VACUUM VERBOSE in the same way? If we do so,
>> autovacuum can handle the reports of VACUUM VERBOSE and plan when to
>> do VACUUM FULL, REINDEX and/or CLUSTER using the information.
>> Is this worth doing?
> You mean having VACUUM VERBOSE return a result set?
To me, the point of VACUUM VERBOSE is mostly to give you some
reassurance that it's making progress. If it were returning rows
instead of notice messages, you'd lose that functionality (at least
in libpq-based clients). In any case, autovacuum has other ways
of getting the information without needing a change in user-visible
behavior.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2006-07-24 14:55:47 | Re: Allow commenting of variables in postgresql.conf to - try 4 |
Previous Message | Tom Lane | 2006-07-24 14:49:17 | Re: patch implementing the multi-argument aggregates (SOC project) |
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2006-07-24 14:55:47 | Re: Allow commenting of variables in postgresql.conf to - try 4 |
Previous Message | Tom Lane | 2006-07-24 14:49:17 | Re: patch implementing the multi-argument aggregates (SOC project) |