Re: Exposing keywords to clients - Mailing list pgsql-patches

From Tom Lane
Subject Re: Exposing keywords to clients
Date
Msg-id 28825.1209774370@sss.pgh.pa.us
Whole thread Raw
In response to Re: Exposing keywords to clients  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-patches
Alvaro Herrera <alvherre@commandprompt.com> writes:
> FWIW pg_dump has fmtId() which does something related.

> I think it's a bit bogus to be using the list as compiled client-side,
> precisely due to the theoretical chance that it could change from one
> server version to the next, but it's probably not very likely that we
> ever remove a keyword from the server grammar.

Actually, it's 100% intentional that pg_dump does it that way --- I
would not support modifying it to use this function (even if it existed
in the back branches).  The reason is exactly that pg_dump wants to
generate output that is correct for its own PG version, not that of the
server it's dumping from.

The tradeoffs are probably different for pgAdmin, but it is important to
realize that either way might be the best thing for a particular case.

            regards, tom lane

pgsql-patches by date:

Previous
From: Tom Lane
Date:
Subject: Re: plpgsql RETURN QUERY EXECUTE
Next
From: Andrew Dunstan
Date:
Subject: Re: [COMMITTERS] pgsql: Sigh ...