pgsql: Fix inconsistent code with shared invalidations of snapshots

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Fix inconsistent code with shared invalidations of snapshots
Date: 2020-12-28 13:19:08
Message-ID: E1ktsQW-0001N4-B7@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Fix inconsistent code with shared invalidations of snapshots

The code in charge of processing a single invalidation message has been
using since 568d413 the structure for relation mapping messages. This
had fortunately no consequence as both locate the database ID at the
same location, but it could become a problem in the future if this area
of the code changes.

Author: Konstantin Knizhnik
Discussion: https://postgr.es/m/8044c223-4d3a-2cdb-42bf-29940840ce94@postgrespro.ru
Backpatch-through: 9.5

Branch
------
REL_13_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/30803bd1cd6c4c9a0dc3362b02b6aa549b876d77

Modified Files
--------------
src/backend/utils/cache/inval.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Andrew Dunstan 2020-12-28 13:49:09 Re: pgsql: Add pg_alterckey utility to change the cluster key
Previous Message Fujii Masao 2020-12-28 11:04:30 pgsql: postgres_fdw: Fix connection leak.