| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | pgsql-committers(at)postgresql(dot)org |
| Subject: | pgsql: Fix btmarkpos/btrestrpos to handle array keys. |
| Date: | 2012-09-27 21:01:24 |
| Message-ID: | E1THLD2-00066I-Uu@gemulon.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Fix btmarkpos/btrestrpos to handle array keys.
This fixes another error in commit 9e8da0f75731aaa7605cf4656c21ea09e84d2eb1.
I neglected to make the mark/restore functionality save and restore the
current set of array key values, which led to strange behavior if an
IndexScan with ScalarArrayOpExpr quals was used as the inner side of a
mergejoin. Per bug #7570 from Melese Tesfaye.
Branch
------
REL9_2_STABLE
Details
-------
http://git.postgresql.org/pg/commitdiff/f2366e584aea41b980f23fcf0a2e118efd7fb09b
Modified Files
--------------
src/backend/access/nbtree/nbtree.c | 8 ++++
src/backend/access/nbtree/nbtutils.c | 59 ++++++++++++++++++++++++++++++++++
src/include/access/nbtree.h | 3 ++
3 files changed, 70 insertions(+), 0 deletions(-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2012-09-28 00:24:15 | pgsql: Produce textual error messages for LDAP issues instead of numeri |
| Previous Message | Alvaro Herrera | 2012-09-27 19:20:10 | pgsql: Have pg_terminate/cancel_backend not ERROR on non-existent proce |