pgsql: Add a defense to prevent storing pseudo-type data into index

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Add a defense to prevent storing pseudo-type data into index
Date: 2008-10-14 21:47:39
Message-ID: 20081014214739.DE6C97545A4@cvs.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Log Message:
-----------
Add a defense to prevent storing pseudo-type data into index columns.
Formerly, the lack of any opclasses that could accept such data was enough
of a defense, but now with a "record" opclass we need to check more carefully.
(You can still use that opclass for an index, but you have to store a named
composite type not an anonymous one.)

Modified Files:
--------------
pgsql/src/backend/catalog:
index.c (r1.305 -> r1.306)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/catalog/index.c?r1=1.305&r2=1.306)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2008-10-14 23:27:40 pgsql: Make the system-attributes loop in AddNewAttributeTuples depend
Previous Message Tom Lane 2008-10-14 21:39:42 pgsql: Update citext expected output for recent change in error message