From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Andy Lester <andy(at)petdance(dot)com> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #5932: CLUSTER doesn't update n_dead_tup |
Date: | 2011-09-06 14:04:42 |
Message-ID: | 201109061404.p86E4gH16362@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
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 code
> > (cluster_rel()). Is this a bug?
>
> I can't imagine how it NOT be a bug to do something that gets rid of dead tuples and then tell the user there are dead tuples when there are actually no dead tuples.
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.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
From | Date | Subject | |
---|---|---|---|
Next Message | Andy Lester | 2011-09-06 14:07:46 | Re: BUG #5932: CLUSTER doesn't update n_dead_tup |
Previous Message | Hadmut | 2011-09-06 11:55:09 | BUG #6199: Can't install datatype hstore |