From: | Michael Paquier <michael(at)paquier(dot)xyz> |
---|---|
To: | Noah Misch <noah(at)leadboat(dot)com> |
Cc: | pgsql-committers(at)lists(dot)postgresql(dot)org |
Subject: | Re: pgsql: Skip WAL for new relfilenodes, under wal_level=minimal. |
Date: | 2020-04-24 07:29:41 |
Message-ID: | 20200424072941.GQ33034@paquier.xyz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Hi Noah,
On Sat, Apr 04, 2020 at 08:40:43PM +0000, Noah Misch wrote:
> Skip WAL for new relfilenodes, under wal_level=minimal.
>
> Until now, only selected bulk operations (e.g. COPY) did this. If a
> given relfilenode received both a WAL-skipping COPY and a WAL-logged
> operation (e.g. INSERT), recovery could lose tuples from the COPY. See
> src/backend/access/transam/README section "Skipping WAL for New
> RelFileNode" for the new coding rules. Maintainers of table access
> methods should examine that section.
>
> To maintain data durability, just before commit, we choose between an
> fsync of the relfilenode and copying its contents to WAL. A new GUC,
> wal_skip_threshold, guides that choice. If this change slows a workload
> that creates small, permanent relfilenodes under wal_level=minimal, try
> adjusting wal_skip_threshold. Users setting a timeout on COMMIT may
> need to adjust that timeout, and log_min_duration_statement analysis
> will reflect time consumption moving to COMMIT from commands like COPY.
+ /*
+ * Records other than SWITCH_WAL must have content. We use an integer 0 to
+ * follow the restriction.
+ */
This commit has added the following comment, but I guess you meant
XLOG_SWITCH instead?
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2020-04-24 07:59:29 | pgsql: Update Unicode data to Unicode 13.0.0 and CLDR 37 |
Previous Message | Michael Paquier | 2020-04-24 02:35:13 | pgsql: Remove some unstable parts from new TAP test for archive status |