pgsql: Allow binary-coercible cases in ri_HashCompareOp; there are some

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Allow binary-coercible cases in ri_HashCompareOp; there are some
Date: 2009-11-05 04:38:35
Message-ID: 20091105043835.ABA84753FB7@cvs.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Log Message:
-----------
Allow binary-coercible cases in ri_HashCompareOp; there are some such cases
that are not handled by find_coercion_pathway, notably composite->RECORD.
Now that 8.4 supports composites as primary keys, it's worth dealing with
this case.

Tags:
----
REL8_4_STABLE

Modified Files:
--------------
pgsql/src/backend/utils/adt:
ri_triggers.c (r1.113 -> r1.113.2.1)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/adt/ri_triggers.c?r1=1.113&r2=1.113.2.1)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2009-11-05 16:58:36 pgsql: Remove plpgsql's RENAME declaration, which has bizarre and mostly
Previous Message Tom Lane 2009-11-05 04:38:29 pgsql: Allow binary-coercible cases in ri_HashCompareOp; there are some