Andy Lester wrote:
>
> On Sep 6, 2011, at 9:04 AM, Bruce Momjian wrote:
>
> > Well, if you TRUNCATE I don't think it updates the statistics either. I
> > think we assume the autovacuum system will analyse the new table soon.
>
>
> When I brought this up in IRC, I recall that that sentiment was
On Sep 6, 2011, at 9:04 AM, Bruce Momjian wrote:
> Well, if you TRUNCATE I don't think it updates the statistics either. I
> think we assume the autovacuum system will analyse the new table soon.
When I brought this up in IRC, I recall that that sentiment was expressed,
along with the standar
Andy Lester wrote:
>
> On Sep 5, 2011, at 3:19 PM, Bruce Momjian wrote:
>
> >
> > This is an interesting bug report from March that got no replies. In my
> > testing, not only does CLUSTER not update the n_dead_tup statistics, but
> > neither does VACUUM FULL, which internally uses the CLUSTER
On Sep 5, 2011, at 3:19 PM, Bruce Momjian wrote:
>
> This is an interesting bug report from March that got no replies. In my
> testing, not only does CLUSTER not update the n_dead_tup statistics, but
> neither does VACUUM FULL, which internally uses the CLUSTER code
> (cluster_rel()). Is this
This is an interesting bug report from March that got no replies. In my
testing, not only does CLUSTER not update the n_dead_tup statistics, but
neither does VACUUM FULL, which internally uses the CLUSTER code
(cluster_rel()). Is this a bug?
-
The following bug has been logged online:
Bug reference: 5932
Logged by: Andy Lester
Email address: a...@petdance.com
PostgreSQL version: 9.0
Operating system: Linux
Description:CLUSTER doesn't update n_dead_tup
Details:
The CLUSTER command does not update the resul
