pgsql: Fix pg_visibility regression failure with CLOBBER_CACHE_ALWAYS

From: Tomas Vondra <tomas(dot)vondra(at)postgresql(dot)org>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Fix pg_visibility regression failure with CLOBBER_CACHE_ALWAYS
Date: 2021-06-08 17:38:53
Message-ID: E1lqfgj-0004RE-T6@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Fix pg_visibility regression failure with CLOBBER_CACHE_ALWAYS

Commit 8e03eb92e9 reverted a bit too much code, reintroducing one of the
issues fixed by 39b66a91bd - a page might have been left partially empty
after relcache invalidation.

Reported-By: Tom Lane
Author: Masahiko Sawada
Discussion: https://postgr.es/m/822752.1623032114@sss.pgh.pa.us
Discussion: https://postgr.es/m/CAD21AoA%3D%3Df2VSw3c-Cp_y%3DWLKHMKc1D6s7g3YWsCOvgaYPpJcg%40mail.gmail.com

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/d1f0aa7696917213485c03b076b573497a535076

Modified Files
--------------
src/backend/access/heap/hio.c | 22 +++++++++++-----------
1 file changed, 11 insertions(+), 11 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Tomas Vondra 2021-06-08 18:28:45 pgsql: Adjust batch size in postgres_fdw to not use too many parameters
Previous Message Tom Lane 2021-06-08 15:59:40 pgsql: Don't crash on empty statements in SQL-standard function bodies.