On 05-01-2015 10:02, Michael Paquier wrote:
On Mon, Jan 5, 2015 at 6:51 PM, Edson Carlos Ericksson Richter
wrote:
Would this kind of count being recorded somewhere else?
How does the server knows that the wal_segments have been exhausted?
You should evaluate the amount of wal_keep_segments nec
On Mon, Jan 5, 2015 at 6:51 PM, Edson Carlos Ericksson Richter
wrote:
> Would this kind of count being recorded somewhere else?
> How does the server knows that the wal_segments have been exhausted?
You should evaluate the amount of wal_keep_segments necessary using
the replication lag in terms of
On 05-01-2015 02:08, Michael Paquier wrote:
On Sun, Jan 4, 2015 at 1:48 AM, Edson Carlos Ericksson Richter
wrote:
How to query current segments allocation relative to "Wal keep segments" in
each master server?
What is your server version? You can have a look at
pg_stat_replication on the mast
On Sun, Jan 4, 2015 at 1:48 AM, Edson Carlos Ericksson Richter
wrote:
> How to query current segments allocation relative to "Wal keep segments" in
> each master server?
What is your server version? You can have a look at
pg_stat_replication on the master which contains information about the
WAL
I'm maintaining async replication (streaming) between four database
servers arranged on 2 x 2.
How to query current segments allocation relative to "Wal keep
segments" in each master server?
I want to add this query to Postbix in order to monitor if the "wal keep
segments" parameter is too shor
