pgsql: For 11 only, put back heap_expand_tuple to GetTupleForTrigger().

From: Andres Freund <andres(at)anarazel(dot)de>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: For 11 only, put back heap_expand_tuple to GetTupleForTrigger().
Date: 2019-02-09 10:52:30
Message-ID: E1gsQFK-00069v-1w@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

For 11 only, put back heap_expand_tuple to GetTupleForTrigger().

This is not necessary anymore after 297d627e, but extensions that have
not been recompiled after the fix will not use the new definition of
heap_getattr(). While recompiling those extensions is obviously the
suggested course, it's cheap enough to retain the expansion in
GetTupleForTrigger().

Per suggestion from Andrew Gierth.

Discussion: 87va1x43ot(dot)fsf(at)news-spur(dot)riddles(dot)org(dot)uk

Branch
------
REL_11_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/920311ab18aac799aee6ad2303b2ed2b6b44c1b8

Modified Files
--------------
src/backend/commands/trigger.c | 10 +++++++++-
1 file changed, 9 insertions(+), 1 deletion(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Peter Eisentraut 2019-02-09 14:57:27 pgsql: Use better comment marker in Autoconf input
Previous Message Andres Freund 2019-02-09 09:38:56 pgsql: Plug leak in BuildTupleHashTable by creating ExprContext in corr