> ________________________________
> From: Антон Тарабрин <taraban...@gmail.com>
> To: "pgsql-general@postgresql.org" <pgsql-general@postgresql.org>
> Sent: Tuesday, 14 March 2017, 14:05
> Subject: Re: [GENERAL] Table not cleaning up drom dead tuples
>
>
> Yep. VACUUM FULL not helping us on OLD table, that are not getting updated
> and not used in any requests. Bloat is still there
> This is production system, so now we are investigating why it's happening.
>
>
> > Information about problematic tables:
> > https://gist.github.com/tarabanton/edf7f8dc26eb7ec37a9cfa3424493871
> At the link above is some results of VACUUM (ANALYZE, VERBOSE) from source
> (OLD) table.
>
So what's the output of vacuum full? Or are you saying you can't sustain the
exclusive lock vacuum full would require?
Plain vacuum can only reclaim free space at the end of the table, fragmented
dead rows can only be marked available for reuse.
Perhaps give us some idea of activity on your database/tables:
select * from pg_stat_user_tables where relname in
('__orders_y2017_m3_to_drop', '__orders_y2017_m2_to_drop');
select * from pg_stat_database;
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
