Skip site navigation (1) Skip section navigation (2)

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 (view raw or flat)
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

pgsql-hackers by date

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

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group