pgsql: Perform post-escaping encoding validity checks on SQL literals - Mailing list pgsql-committers

From adunstan@postgresql.org (Andrew Dunstan)
Subject pgsql: Perform post-escaping encoding validity checks on SQL literals
Date
Msg-id 20070912204927.7E88C753DF9@cvs.postgresql.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
Perform post-escaping encoding validity checks on SQL literals and COPY input
so that invalidly encoded data cannot enter the database by these means.

Modified Files:
--------------
    pgsql/src/backend/commands:
        copy.c (r1.286 -> r1.287)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/copy.c?r1=1.286&r2=1.287)
    pgsql/src/backend/parser:
        scan.l (r1.140 -> r1.141)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/scan.l?r1=1.140&r2=1.141)

pgsql-committers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: pgsql: Release the exclusive lock on the table early after truncating it
Next
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Redefine the lp_flags field of item pointers as having four