Skip site navigation (1) Skip section navigation (2)

pgsql: Consolidate and improve checking of key-column-attnum arguments

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Consolidate and improve checking of key-column-attnum arguments
Date: 2010-06-15 16:22:45
Message-ID: 20100615162245.489D57541D4@cvs.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-committers
Log Message:
-----------
Consolidate and improve checking of key-column-attnum arguments for
dblink_build_sql_insert() and related functions.  In particular, be sure to
reject references to dropped and out-of-range column numbers.  The numbers
are still interpreted as physical column numbers, though, for backward
compatibility.

This patch replaces Joe's patch of 2010-02-03, which handled only some aspects
of the problem.

Tags:
----
REL8_1_STABLE

Modified Files:
--------------
    pgsql/contrib/dblink:
        dblink.c (r1.48.2.9 -> r1.48.2.10)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/contrib/dblink/dblink.c?r1=1.48.2.9&r2=1.48.2.10)
    pgsql/contrib/dblink/expected:
        dblink.out (r1.16.2.2 -> r1.16.2.3)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/contrib/dblink/expected/dblink.out?r1=1.16.2.2&r2=1.16.2.3)

pgsql-committers by date

Next:From: Tom LaneDate: 2010-06-15 16:22:51
Subject: pgsql: Consolidate and improve checking of key-column-attnum arguments
Previous:From: Tom LaneDate: 2010-06-15 16:22:39
Subject: pgsql: Consolidate and improve checking of key-column-attnum arguments

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group