| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Fabrízio de Royes Mello <fabriziomello(at)gmail(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Verbose output of pg_dump not show schema name |
| Date: | 2014-04-17 15:46:39 |
| Message-ID: | 20140417154639.GF7443@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Apr 17, 2014 at 11:44:37AM -0400, Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)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(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has their own god. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2014-04-17 15:56:15 | Re: shouldn't we log permission errors when accessing the configured trigger file? |
| Previous Message | Bruce Momjian | 2014-04-17 15:45:42 | Re: pg_upgrade & tablespaces |