| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Michael Meskes <meskes(at)postgresql(dot)org> |
| Cc: | PostgreSQL Hacker <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: scan.l: check_escape_warning() |
| Date: | 2008-01-14 19:31:04 |
| Message-ID: | 23823.1200339064@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Michael Meskes <meskes(at)postgresql(dot)org> writes:
> On Fri, Jan 11, 2008 at 10:41:17AM -0500, Tom Lane wrote:
>> Perhaps there's some discrepancy between the ecpg and backend lexers
>> as to where these are called?
> You're right. There is no way to (un)select standard conforming strings
> which makes up for the difference.
If that's how it is going to be, would you remove or #ifdef NOT_USED
the escape_string_warning function? The 'function defined but not used'
warning that it's producing now is kind of annoying ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Warren Turkal | 2008-01-14 19:33:56 | Re: timestamp refactor effort |
| Previous Message | Tom Lane | 2008-01-14 18:46:17 | pgsql: Fix an ancient oversight in libpq's handling of V3-protocol COPY |