From: | Dmitriy Sarafannikov <d(dot)sarafannikov(at)bk(dot)ru> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re[2]: [BUGS] Too many files in pg_replslot folder |
Date: | 2016-03-11 08:16:51 |
Message-ID: | 1457684211.431682571@f351.i.mail.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
> Well, the files are all different in what you reported, so I would say
> it's not a loop but a very long sequence.
Yes, i have noticed this, sorry for bad explanation.
> This can happen if you have a very long transaction while the snapshot
> for the slot is being built, and a million other transactions happen
> before the long transaction commits. One way in which this would go on
> and on until it fills the disk is that you have a prepared transaction
> that you forgot about (See select * from pg_prepared_xacts to diagnose
> this one). Or you could just have a very long transaction (see select *
> from pg_stat_activity).
Thanks for explanation. Where was a long autovacuum on big table.
What will happen when he finished?
Wal sender will remove all of this files together and will utilze disk on 100% again?
Regards,
Dmitriy Sarafannikov
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2016-03-11 11:01:43 | Re: BUG #13854: SSPI authentication failure: wrong realm name used |
Previous Message | jkoceniak | 2016-03-10 20:50:29 | BUG #14015: Query Plan not optimal |