| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Subject: | Re: quoting psql varible as identifier |
| Date: | 2009-12-29 20:05:53 |
| Message-ID: | 162867790912291205l2e5b2cabm412756da49464e6e@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
2009/12/29 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> writes:
>> 2009/12/29 Alvaro Herrera <alvherre(at)commandprompt(dot)com>:
>>> Can we use a trick similar to pg_dump's?
>
>> I see it - we can move function (content) fmtId from dumputils.c to libpq.
>
> This is not a good idea. pg_dump can be expected to be up-to-date with
> the backend's keyword list, but libpq cannot.
>
> Just quote the thing unconditionally. It's not worth working harder
> than that anyway.
I see it.
Pavel
>
> regards, tom lane
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2009-12-29 20:19:57 | Re: quoting psql varible as identifier |
| Previous Message | Tom Lane | 2009-12-29 19:57:23 | Re: quoting psql varible as identifier |