Re: psql \dFp's behavior

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Guillaume Lelarge <guillaume(at)lelarge(dot)info>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: psql \dFp's behavior
Date: 2007-12-11 20:16:33
Message-ID: 5970.1197404193@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Guillaume Lelarge <guillaume(at)lelarge(dot)info> writes:
> I'm not sure psql handles \dFp the right way. The query allows
> translators to translate some columns' values but forgets to escape the
> strings. So, here is a patch that escapes these translated strings.

This seems mighty ugly, and it's not the way we handle any other \d
command. Why is it needed for \dFp (and only that)?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Guillaume Lelarge 2007-12-11 20:50:53 Re: psql \dFp's behavior
Previous Message Tom Lane 2007-12-11 20:06:51 Re: archive_command failures report confusing exit status