pgsql: Fix failure-to-copy bug in commit 6f6b99d13.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Fix failure-to-copy bug in commit 6f6b99d13.
Date: 2017-09-09 00:45:38
Message-ID: E1dqTty-0006tL-Sx@gemulon.postgresql.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Fix failure-to-copy bug in commit 6f6b99d13.

The previous coding of get_qual_for_list() was careful to copy everything
it was using from the input data structure. The new version missed
making a copy of pass-by-ref datum values that it's inserting into Consts.
This is not optional, however, as revealed by buildfarm failures on
machines running -DRELCACHE_FORCE_RELEASE: we're copying from a relcache
entry that could go away before the required lifespan of our output
expression. I'm pretty sure -DCLOBBER_CACHE_ALWAYS machines won't like
this either, but none of them have reported in yet.

Branch
------
master

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

Modified Files
--------------
src/backend/catalog/partition.c | 10 ++++++++--
1 file changed, 8 insertions(+), 2 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Peter Eisentraut 2017-09-09 21:46:00 pgsql: pg_upgrade: Message style fixes
Previous Message Robert Haas 2017-09-09 00:08:25 Re: pgsql: Allow a partitioned table to have a default partition.