pgsql: Fix failure to mark init buffers as BM_PERMANENT.

From: Robert Haas <rhaas(at)postgresql(dot)org>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Fix failure to mark init buffers as BM_PERMANENT.
Date: 2017-03-14 16:13:04
Message-ID: E1cnp4K-0006pH-58@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Fix failure to mark init buffers as BM_PERMANENT.

This could result in corruption of the init fork of an unlogged index
if the ambuildempty routine for that index used shared buffers to
create the init fork, which was true for gin, gist, and hash indexes.

Patch by me, based on an earlier patch by Michael Paquier, who also
reviewed this one. This also incorporates an idea from Artur
Zakirov.

Discussion: http://postgr.es/m/CACYUyc8yccE4xfxhqxfh_Mh38j7dRFuxfaK1p6dSNAEUakxUyQ@mail.gmail.com

Branch
------
REL9_3_STABLE

Details
-------
http://git.postgresql.org/pg/commitdiff/6bd7816e766abd6c10db16ed0af93a512b1a662d

Modified Files
--------------
src/backend/storage/buffer/bufmgr.c | 7 ++++++-
src/include/storage/buf_internals.h | 2 +-
2 files changed, 7 insertions(+), 2 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Robert Haas 2017-03-14 16:19:17 pgsql: Update .gitignore
Previous Message Peter Eisentraut 2017-03-14 15:19:30 pgsql: doc: Fix synopsis