database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-05-02 11:44:50 +03:00
Code

Fix testlibpq3

Browse Source 
The sample output assumes non-standard-conforming interpretation of
backslashes in input literals, so the actual output didn't match.

Noticed while perusing another patch that touches this file.

Evidently this code is seldom checked, so I'm not going to bother
backpatching this fix.
This commit is contained in:
Alvaro Herrera 2019-09-18 16:29:55 -03:00
parent 32200c19dd
commit 9b8e99e905
2 changed files with 5 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
src/test/examples/testlibpq3.c
View File

@ -11,8 +11,8 @@
* CREATE SCHEMA testlibpq3; * CREATE SCHEMA testlibpq3;
* SET search_path = testlibpq3; * SET search_path = testlibpq3;
* CREATE TABLE test1 (i int4, t text, b bytea); * CREATE TABLE test1 (i int4, t text, b bytea);
* INSERT INTO test1 values (1, 'joe''s place', '\\000\\001\\002\\003\\004'); * INSERT INTO test1 values (1, 'joe''s place', '\000\001\002\003\004');
* INSERT INTO test1 values (2, 'ho there', '\\004\\003\\002\\001\\000'); * INSERT INTO test1 values (2, 'ho there', '\004\003\002\001\000');
* *
* The expected output is: * The expected output is:
* *

5
src/test/examples/testlibpq3.sql
View File

@ -1,5 +1,6 @@
CREATE SCHEMA testlibpq3; CREATE SCHEMA testlibpq3;
SET search_path = testlibpq3; SET search_path = testlibpq3;
SET standard_conforming_strings = ON;
CREATE TABLE test1 (i int4, t text, b bytea); CREATE TABLE test1 (i int4, t text, b bytea);
INSERT INTO test1 values (1, 'joe''s place', '\\000\\001\\002\\003\\004'); INSERT INTO test1 values (1, 'joe''s place', '\000\001\002\003\004');
INSERT INTO test1 values (2, 'ho there', '\\004\\003\\002\\001\\000'); INSERT INTO test1 values (2, 'ho there', '\004\003\002\001\000');