Re: Replacing plpgsql's lexer

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: David Fetter <david(at)fetter(dot)org>
Cc: Alvaro Herrera <alvherre(at)commandprompt(dot)com>, pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: Replacing plpgsql's lexer
Date: 2009-04-17 18:14:01
Message-ID: 25705.1239992041@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

David Fetter <david(at)fetter(dot)org> writes:
>> It's hardly a "show stopping bug", considering it's been there since
>> standard_conforming_strings was invented.

> A known sploit would be a show-stopper.

We're not turning on standard_conforming_strings right now. We are
*certainly* not forcing it on without recourse in existing branches,
which would be the logical conclusion if we considered this to be a
security issue fixable in no other way. Would you mind not wasting the
list's time with this?

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2009-04-17 19:28:58 Re: [rfc] unicode escapes for extended strings
Previous Message David Fetter 2009-04-17 18:09:22 Re: Replacing plpgsql's lexer