From: Dmitriy Sarafannikov <d.sarafannikov@bk.ru>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: PostgreSQL Bugs <pgsql-bugs@postgresql.org>
Subject: Re[2]: [BUGS] Too many files in pg_replslot folder
Date: Fri, 11 Mar 2016 11:16:51 +0300
Message-ID: <1457684211.431682571@f351.i.mail.ru> (raw)
In-Reply-To: <20160310153412.GA53338@alvherre.pgsql>
References: <1457621358.355011041@f382.i.mail.ru>
<20160310153412.GA53338@alvherre.pgsql>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-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
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: d.sarafannikov@bk.ru, alvherre@2ndquadrant.com
Subject: Re: Re[2]: [BUGS] Too many files in pg_replslot folder
In-Reply-To: <1457684211.431682571@f351.i.mail.ru>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox