Re: Tracking of page changes for backup purposes. PTRACK [POC]

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Aleksander Alekseev <a(dot)alekseev(at)postgrespro(dot)ru>, Andrey Borodin <x4mmm(at)yandex-team(dot)ru>, Anastasia Lubennikova <a(dot)lubennikova(at)postgrespro(dot)ru>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Tracking of page changes for backup purposes. PTRACK [POC]
Date: 2017-12-19 00:40:17
Message-ID: CAB7nPqSfCsDD7FxR1apL8bfoKm1bjek7QAWK2rW4rTb=t-m8BQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Dec 19, 2017 at 2:57 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> I think this doesn't really show much because it's apparently limited
> by the speed of fsync() on your filesystem. You might try running the
> test with synchronous_commit=off.

You may want to run Postgres on scissors as much as possible by
decreasing checkpoint frequency. etc.

+ /*
+ * Do not track changes for unlogged and temp relations,
+ * since we are not going to backup them anyway.
+ */
+ if (rel->rd_rel->relpersistence != RELPERSISTENCE_PERMANENT)
+ return;
This is not true for init forks of unlogged tables, which are logged
and included in backups.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Langote 2017-12-19 02:48:14 Re: [HACKERS] Add support for tuple routing to foreign partitions
Previous Message Michael Paquier 2017-12-19 00:36:29 Re: Tracking of page changes for backup purposes. PTRACK [POC]