diff options
author | Thomas Munro <tmunro@postgresql.org> | 2022-05-07 15:19:52 +1200 |
---|---|---|
committer | Thomas Munro <tmunro@postgresql.org> | 2022-05-07 16:47:29 +1200 |
commit | e2f65f42555ff531c6d7c8f151526b4ef7c016f8 (patch) | |
tree | 98c40e19efc4aa3c8670317c34261835d75f60c1 /src/backend/access/transam/xlog.c | |
parent | b74e94dc27fdbb13954f230b1d1298430afa6c0c (diff) | |
download | postgresql-e2f65f42555ff531c6d7c8f151526b4ef7c016f8.tar.gz postgresql-e2f65f42555ff531c6d7c8f151526b4ef7c016f8.zip |
Fix old-fd issues using global barriers everywhere.
Commits 4eb21763 and b74e94dc introduced a way to force every backend to
close all relation files, to fix an ancient Windows-only bug.
This commit extends that behavior to all operating systems and adds
a couple of extra barrier points, to fix a totally different class of
bug: the reuse of relfilenodes in scenarios that have no other kind of
cache invalidation to prevent file descriptor mix-ups.
In all releases, data corruption could occur when you moved a database
to another tablespace and then back again. Despite that, no back-patch
for now as the infrastructure required is too new and invasive. In
master only, since commit aa010514, it could also happen when using
CREATE DATABASE with a user-supplied OID or via pg_upgrade.
Author: Andres Freund <andres@anarazel.de>
Reviewed-by: Robert Haas <robertmhaas@gmail.com>
Reviewed-by: Thomas Munro <thomas.munro@gmail.com>
Discussion: https://postgr.es/m/20220209220004.kb3dgtn2x2k2gtdm%40alap3.anarazel.de
Diffstat (limited to 'src/backend/access/transam/xlog.c')
0 files changed, 0 insertions, 0 deletions