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

Re: [COMMITTERS] pgsql: Unicode escapes in E'...' strings Author: Marko Kreen

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Marko Kreen <markokr(at)gmail(dot)com>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [COMMITTERS] pgsql: Unicode escapes in E'...' strings Author: Marko Kreen
Date: 2009-09-25 20:39:36
Message-ID: 3432.1253911176@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-hackers
Marko Kreen <markokr(at)gmail(dot)com> writes:
> On 9/25/09, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> This patch has broken the no-backup property of the scanner, which
>> is an absolutely unacceptable penalty for such a second-order feature.
>> Please fix or revert.

> How do I find out the state of said property?

Per the comment at the head of scan.l, add the -b switch to the flex
call and see what flex says about it.

> Currently I assume its related to xeunicodebad pattern?

Probably, but I didn't check.

			regards, tom lane

In response to

pgsql-hackers by date

Next:From: Peter EisentrautDate: 2009-09-25 20:53:38
Subject: Re: [COMMITTERS] pgsql: Unicode escapes in E'...' strings Author: Marko Kreen
Previous:From: Tom LaneDate: 2009-09-25 20:36:39
Subject: formrdesc() versus relation rowtype OIDs

pgsql-committers by date

Next:From: Peter EisentrautDate: 2009-09-25 20:51:37
Subject: pgsql: Remove backup states from Unicode escapes patch
Previous:From: Marko KreenDate: 2009-09-25 20:23:17
Subject: Re: [COMMITTERS] pgsql: Unicode escapes in E'...' strings Author: Marko Kreen

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