BUG #7505: Backslash escaping not necessary - Mailing list pgsql-bugs

From ovadyaj@gmail.com
Subject BUG #7505: Backslash escaping not necessary
Date
Msg-id E1T502x-0004da-K3@wrigleys.postgresql.org
Whole thread Raw
Responses Re: BUG #7505: Backslash escaping not necessary
List pgsql-bugs
The following bug has been logged on the website:

Bug reference:      7505
Logged by:          Jeff Ovadya
Email address:      ovadyaj@gmail.com
PostgreSQL version: 9.1.4
Operating system:   PostgreSQL 9.1.4, compiled by Visual C++ build 150
Description:        =


INSERT INTO customer VALUES ( 20, 'Mr', 'Jeff', 'Baggott', 'Midtown Street
A\\33', 'Milltown', 'MT9 8NQ', '746 3956'); results in two backslashes
instead of a single one. =


Inserting the address with a single backslash succeeds in saving the
backslash with the address.

Also noticed similar issue escaping single quotes: Backslash will not work
to escape, but doubling up the quotes works.

pgsql-bugs by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: BUG #4958: Stats collector hung on WaitForMultipleObjectsEx while attempting to recv a datagram
Next
From: crispond@gmail.com
Date:
Subject: BUG #7506: Windows 64 bit PGAdmin 1.14.3 plpgsql default parameter value not appearing