From: | Wells Oliver <wells(dot)oliver(at)gmail(dot)com> |
---|---|
To: | pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: pg_repack and table statistics |
Date: | 2024-08-29 04:21:12 |
Message-ID: | CAOC+FBV0Q_E=cMnE4c06yMz-WBg7XbhwCN3Cf09s9GYSU4jRAA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Hmm, apologies, I'd delete this if I could, I was looking at stale data for
pg_stat_user_tables, it indeed has a n_dead_tup of 0 after a repack.
On Wed, Aug 28, 2024 at 9:16 PM Wells Oliver <wells(dot)oliver(at)gmail(dot)com> wrote:
> I find that the n_dead_tup value in pg_stat_user_tables is the same before
> and after a successful pg_repack of that table (ditto all the values
> really). Is there something that should be done after a repack to have
> those stats updated, or is their unchanging value a sign of repack failing
> for some reason?
>
> --
> Wells Oliver
> wells(dot)oliver(at)gmail(dot)com <wellsoliver(at)gmail(dot)com>
>
--
Wells Oliver
wells(dot)oliver(at)gmail(dot)com <wellsoliver(at)gmail(dot)com>
From | Date | Subject | |
---|---|---|---|
Next Message | Laurenz Albe | 2024-08-29 10:56:16 | Re: Password Change Mandatory during First Login |
Previous Message | Wells Oliver | 2024-08-29 04:16:31 | pg_repack and table statistics |