Re: [GENERAL] [PERFORM] Questionaire: Common WAL write rates on busy servers.

Hi Andres. > 25 апр. 2017 г., в 7:17, Andres Freund написал(а): > > Hi, > > I've lately seen more and more installations where the generation of > write-ahead-log (WAL) is one of the primary bottlenecks. I'm curious > whether that's primarily a "sampling error" of mine, or

[GENERAL] Way to get timeline

Hi all. What is the best way to get current timeline of host? Right now I can imagine two variants: 1. Do checkpoint and read it from control file. 2. Do something like SELECT substr(pg_xlogfile_name(pg_current_xlog_location()), 1, 8). Both variants seem to be a bit tricky. Is there a way

Re: [GENERAL] [pgadmin-support] Issue with a hanging apply process on the replica db after vacuum works on primary

19 марта 2015 г., в 20:30, Sergey Shchukin shchukin@gmail.com написал(а): 17.03.2015 13:22, Sergey Shchukin пишет: 05.03.2015 11:25, Jim Nasby пишет: On 2/27/15 5:11 AM, Sergey Shchukin wrote: show max_standby_streaming_delay; max_standby_streaming_delay

Re: [GENERAL] Check that streaming replica received all data after master shutdown

05 янв. 2015 г., в 18:15, Vladimir Borodin r...@simply.name написал(а): Hi all. I have a simple script for planned switchover of PostgreSQL (9.3 and 9.4) master to one of its replicas. This script checks a lot of things before doing it and one of them is that all data from master has

[GENERAL] Check that streaming replica received all data after master shutdown

Hi all. I have a simple script for planned switchover of PostgreSQL (9.3 and 9.4) master to one of its replicas. This script checks a lot of things before doing it and one of them is that all data from master has been received by replica that is going to be promoted. Right now the check is