pgsql: Fix over-optimistic caching in fetch_array_arg_replace_nulls().

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Fix over-optimistic caching in fetch_array_arg_replace_nulls().
Date: 2015-02-25 19:19:19
Message-ID: E1YQhUN-0007WS-OR@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Fix over-optimistic caching in fetch_array_arg_replace_nulls().

When I rewrote this in commit 56a79a869bedc4bf6c35853642694cc0b0594dd2,
I forgot that it's possible for the input array type to change from one
call to the next (this can happen when applying the function to
pg_statistic columns, for instance). Fix that.

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/77903ede08845e55bd2a6c99b52d8da6926d6e84

Modified Files
--------------
src/backend/utils/adt/array_userfuncs.c | 36 +++++++++++++++++++------------
1 file changed, 22 insertions(+), 14 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Stephen Frost 2015-02-26 02:36:50 pgsql: Add locking clause for SB views for update/delete
Previous Message Tom Lane 2015-02-25 17:01:40 pgsql: Fix dumping of views that are just VALUES(...) but have column a