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

From: adunstan(at)postgresql(dot)org (Andrew Dunstan)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Perform post-escaping encoding validity checks on SQL literals
Date: 2007-09-12 20:49:27
Message-ID: 20070912204927.7E88C753DF9@cvs.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2007-09-12 22:10:26 pgsql: Redefine the lp_flags field of item pointers as having four
Previous Message Alvaro Herrera 2007-09-12 20:44:03 Re: pgsql: Release the exclusive lock on the table early after truncating it