Re: quoting psql varible as identifier

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
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 19:57:23
Message-ID: 2855.1262116643@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2009-12-29 20:05:53 Re: quoting psql varible as identifier
Previous Message Pavel Stehule 2009-12-29 19:55:34 Re: quoting psql varible as identifier