| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Lee Hachadoorian <Lee(dot)Hachadoorian+L(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: SQL keywords are suddenly case sensitive |
| Date: | 2013-04-17 01:05:49 |
| Message-ID: | 20130417010549.GF4602@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Apr 16, 2013 at 08:57:02PM -0400, Lee Hachadoorian wrote:
>
> On 04/16/2013 08:23 PM, Tom Lane wrote:
> >"SELECT 1" as all one token. Also, if you transcribed this accurately,
> >it looks like the error cursor is pointing to the second character of
> >the "SELECT" not the first (could you confirm that?). Which is even
> >more bizarre.
>
> No, that must have been an email formatting thing. In psql, the
> caret is under the S.
>
> Looking at the other issues you raised, but just wanted to provide a
> quick answer to that.
Use SET log_statment='all' and look in the server logs for the query.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Lee Hachadoorian | 2013-04-17 01:18:59 | Re: SQL keywords are suddenly case sensitive |
| Previous Message | Lee Hachadoorian | 2013-04-17 00:57:02 | Re: SQL keywords are suddenly case sensitive |