That was exactly that one bug. Thanks a lot
вт, 14 марта 2017 г., 23:26 Jeff Janes :
> On Tue, Mar 14, 2017 at 5:09 AM, Антон Тарабрин
> wrote:
>
> Good day. It seems that we have some strange case of VACUUM malfunction
> and table bloating.
>
> PostgreSQL 9.5.3
>
>
> Are you using replication s
On Tue, Mar 14, 2017 at 5:09 AM, Антон Тарабрин
wrote:
> Good day. It seems that we have some strange case of VACUUM malfunction
> and table bloating.
>
> PostgreSQL 9.5.3
>
Are you using replication slots?
See this, fixed in 9.5.5:
commit de396a1cb34626619ddc6fb9dec6d12abee8b589
Author: Andre
Nope, we've checked everything before deciding to write in mail list.
We have no idea why it's happening.
вт, 14 мар. 2017 г. в 19:10, Glyn Astill :
> And no prepared transactions you say?
>
> select * from pg_prepared_xacts;
>
> Perhaps someone else will chime in ...
>
--
__
> We're, in general, pretty carefull with our DB, as it contains important
> data.
> Most rollback is issued by application (which processes all data inside
> transactions).
>
> p.s. Time is in UTC (GMT+0)
>
> =# select min(xact_start) from pg_stat_activity where state<>'idle';
>
We're, in general, pretty carefull with our DB, as it contains important
data.
Most rollback is issued by application (which processes all data inside
transactions).
p.s. Time is in UTC (GMT+0)
=# select min(xact_start) from pg_stat_activity where
state<>'idle';
min
---
> This tables is original ones, it doesn't have any activity now. We copied
> data to NEW tables and trying to solve root of the problem
>
> - target database where broken tables are located
>
>
> - VACUUM FULL VERBOSE
> =# VACUUM (FULL, VERBOSE) __orders_y2017_m2_to_drop;
> INFO: vacuu
This tables is original ones, it doesn't have any activity now. We copied
data to NEW tables and trying to solve root of the problem
- target database where broken tables are located
- VACUUM FULL VERBOSE
=# VACUUM (FULL, VERBOSE) __orders_y2017_m2_to_drop;
INFO: vacuuming "public.__orders_
>
> From: Антон Тарабрин
> To: "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 n
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/edf7f8dc26eb7ec37a9c
> From: Антон Тарабрин
> To: pgsql-general@postgresql.org
> Sent: Tuesday, 14 March 2017, 12:09
> Subject: [GENERAL] Table not cleaning up drom dead tuples
> General info about our database:
> https://gist.github.com/aCLr/dec78ab031749e517550ac11f8233f70
>
> Infor
Good day. It seems that we have some strange case of VACUUM malfunction and
table bloating.
PostgreSQL 9.5.3
OS #uname -a
FreeBSD db-host 10.2-RELEASE-p18 FreeBSD 10.2-RELEASE-p18 #0: Sat May 28
08:53:43 UTC 2016
r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC
amd64
General info a
11 matches
Mail list logo
