pgsql: Fix access to just-closed relcache entry.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Fix access to just-closed relcache entry.
Date: 2018-06-11 23:18:12
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-committers

Fix access to just-closed relcache entry.

It might be impossible for this to cause a problem in non-debug builds,
since there'd be no opportunity for the relcache entry to get recycled
before the fetch. It blows up nicely with -DRELCACHE_FORCE_RELEASE plus
valgrind, though.

Evidently introduced by careless refactoring in commit f0e44751d.
Back-patch accordingly.




Modified Files
src/backend/commands/tablecmds.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Peter Eisentraut 2018-06-12 01:36:44 pgsql: doc: Suggest logical replication more prominently for upgrading
Previous Message Andres Freund 2018-06-11 23:16:34 Re: [COMMITTERS] pgsql: Logical replication