pgsql: Fix up gincostestimate for new extractQuery API.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Fix up gincostestimate for new extractQuery API.
Date: 2011-01-09 01:27:27
Message-ID: E1Pbk47-0002QD-IW@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Fix up gincostestimate for new extractQuery API.

The only reason this wasn't crashing while testing the core anyarray
operators was that it was disabled for those cases because of passing the
wrong type information to get_opfamily_proc :-(. So fix that too, and make
it insist on finding the support proc --- in hindsight, silently doing
nothing is not as sane a coping mechanism as all that.

Branch
------
master

Details
-------
http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=4d1b76e49eb848b046ddb1beb0f4589816ec8261

Modified Files
--------------
src/backend/utils/adt/selfuncs.c | 65 +++++++++++++++++++++++++-------------
1 files changed, 43 insertions(+), 22 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2011-01-09 05:39:39 pgsql: Fix assorted corner-case bugs in contrib/intarray.
Previous Message Michael Meskes 2011-01-08 22:05:10 pgsql: In ecpg's parser removed a fixed length limit for constants defi