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

From tgl@postgresql.org (Tom Lane)
Subject pgsql: Add a defense to prevent storing pseudo-type data into index
Date
Msg-id 20081014214739.DE6C97545A4@cvs.postgresql.org
Whole thread Raw
List 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)

pgsql-committers by date:

Previous
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Update citext expected output for recent change in error message
Next
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Make the system-attributes loop in AddNewAttributeTuples depend