ns of serializable transactions that could live for a 1
billion xids.
--
Pavel Suderevsky
E: psuderevsky(at)gmail(dot)com
вт, 9 апр. 2019 г. в 16:00, Pavel Suderevsky :
> On Sun, Apr 7, 2019 at 2:31 AM Pavel Suderevsky
>> wrote:
>> > Probably if you advise me what could cause
Hi,
PostgreSQL 11.6
Centos 7.6
pgBackrest 2.19
Case:
Master is on timeline 15 while Standby that should be synchronized with
Master as a hot standby is on timeline 13. WALs to be obtained from archive.
recovery.conf:
>primary_conninfo = 'user=usename host=10.10.10.3 port=5432 sslmode=prefer
app
t; from archive
>
Command:
*restore_command = 'echo -e "Searching WAL: %f, location: %p";
/usr/bin/pgbackrest --stanza=platform archive-get %f "%p"'*
As you can see Postgres tries restoring* 0022** WALs *before timeline
switch LSN* is reached while restorin
gepages" pages exceeded? It looks like
much more value than VmPeak must be set to guarantee reliability.
Thanks,
Pavel Suderevsky
LATION LEVEL'?
Thank you very much in advance.
--
Pavel Suderevsky
Hi,
PG: 9.6.11
OS: CentOS
Env: AWS EC2
I've faced the following exceptions in PostgreSQL server log:
> could not truncate directory "pg_serial": apparent wraparound
Sometimes it repeats every 5 min and the longest period was 40 min.
In fact, I can't find any suspicious events happening that peri
ed at max and 30k in average. Probably because of high CPU usage some
statements were spending a lot of time in bind/parse steps.
Probably if you advise me what could cause *"pg_serial": apparent
wraparound* messages I would have more chances to handle all the
performance issues.
Thank you!
-
>
> On Sun, Apr 7, 2019 at 2:31 AM Pavel Suderevsky
> wrote:
> > Probably if you advise me what could cause "pg_serial": apparent
> wraparound messages I would have more chances to handle all the performance
> issues.
>
> Did you see that warning at some p
