Re: Verbose output of pg_dump not show schema name

Поиск
Список
Период
Сортировка
От Bruce Momjian
Тема Re: Verbose output of pg_dump not show schema name
Дата
Msg-id 20140417154639.GF7443@momjian.us
обсуждение исходный текст
Ответ на Re: Verbose output of pg_dump not show schema name  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: Verbose output of pg_dump not show schema name  (Fabrízio de Royes Mello <fabriziomello@gmail.com>)
Список pgsql-hackers
On Thu, Apr 17, 2014 at 11:44:37AM -0400, Tom Lane wrote:
> Bruce Momjian <bruce@momjian.us> writes:
> > The idea is that we only need quotes when there are odd characters in
> > the identifier.  We do that right now in some places, though I can't
> > find them in pg_dump.  I know psql does that, see quote_ident().
> 
> I think our general style rule is that identifiers embedded in messages
> are always double-quoted.  There's an exception for type names, but
> not otherwise.  You're confusing the message case with printing SQL.

OK.  I was unclear if a status _display_ was a message like an error
message.

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + Everyone has their own god. +



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Bruce Momjian
Дата:
Сообщение: Re: [GENERAL] pg_upgrade & tablespaces
Следующее
От: Bruce Momjian
Дата:
Сообщение: Re: shouldn't we log permission errors when accessing the configured trigger file?