| From: | Ants Aasma <ants(dot)aasma(at)eesti(dot)ee> |
|---|---|
| To: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Hooks to track changed pages for backup purposes |
| Date: | 2017-09-13 10:43:07 |
| Message-ID: | CA+CSw_vFZ69mGf-8YMo+=dJ8LMjH1nUdaau_qpjpPQmBW=4srw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Aug 31, 2017 at 9:02 AM, Andrey Borodin <x4mmm(at)yandex-team(dot)ru> wrote:
> When we have accumulated diff blocknumbers for most of segments we can significantly speed up method of WAL scanning. If we have blocknumbers for all segments we can skip WAL scanning at all.
Have you measured that the WAL scanning is actually a significant
issue? As a quick experiment I hacked up pg_waldump to just dump block
references to stdout in binary format. It scanned 2.8GB of WAL in 3.17
seconds, outputting 9.3M block refs per second. WAL was generated with
pgbench, synchronous commit off, using 4 cores for 10 minutes - making
the ratio of work from generating WAL to parsing it be about 750:1.
Regards,
Ants Aasma
| From | Date | Subject | |
|---|---|---|---|
| Next Message | amul sul | 2017-09-13 10:54:28 | Re: UPDATE of partition key |
| Previous Message | Ashutosh Sharma | 2017-09-13 10:39:20 | Re: Getting error message with latest PG source on Windows. |