From: | Sergey Burladyan <eshkinkot(at)gmail(dot)com> |
---|---|
To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Dmitriy Sarafannikov <dsarafannikov(at)yandex(dot)ru>, Vladimir Borodin <root(at)simply(dot)name> |
Subject: | Re: Broken hint bits (freeze) |
Date: | 2017-06-20 16:24:49 |
Message-ID: | 87tw3a62zy.fsf@seb.koffice.internal |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> writes:
> > I am not sure about rsync, in my production server I have for example
> > 111 GB in pg_xlog and if I run rsync for pg_xlog it must send ~ 40GB
> > of new WALs I think.
> >
>
> Isn't the difference between old and new is just the last WAL segment
> file? What is the source of this difference?
Postgres generate WAL files forward, and at standby too :-(
For example:
=== master ===
$ psql -c 'select pg_current_xlog_insert_location()'
pg_current_xlog_insert_location
---------------------------------
4ED09/34A74590
(1 row)
$ ls 9.2/main/pg_xlog/ | awk '/4ED0900000034/,/xxx/ { print }' | wc -l
2262
==============
=== standby ===
$ psql -c 'select pg_last_xlog_replay_location()'
pg_last_xlog_replay_location
------------------------------
4ED0A/AECFD7B8
(1 row)
postgres(at)avi-sql29:~$ ls 9.2/main/pg_xlog/ | awk '/4ED0A000000AE/,/xxx/ { print }' | wc -l
2456
===============
See https://www.postgresql.org/docs/9.2/static/wal-configuration.html
> they are recycled (renamed to become the next segments in the numbered sequence)
--
Sergey Burladyan
From | Date | Subject | |
---|---|---|---|
Next Message | Merlin Moncure | 2017-06-20 16:33:30 | postgresql transactons not fully isolated |
Previous Message | Bruce Momjian | 2017-06-20 16:09:02 | Re: Broken hint bits (freeze) |