| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Daniel Verite" <daniel(at)manitou-mail(dot)org> |
| Cc: | "Fabien COELHO" <coelho(at)cri(dot)ensmp(dot)fr>, "Robert Haas" <robertmhaas(at)gmail(dot)com>, "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com>, "Corey Huinker" <corey(dot)huinker(at)gmail(dot)com>, "PostgreSQL Developers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Variable substitution in psql backtick expansion |
| Date: | 2017-09-05 14:54:51 |
| Message-ID: | 30116.1504623291@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I wrote:
> "Daniel Verite" <daniel(at)manitou-mail(dot)org> writes:
>> That would look like the following, for example, with a 3-space margin
>> for the description:
>> AUTOCOMMIT
>> If set, successful SQL commands are automatically committed
> But we could do something close to that, say two-space indent for the
> variable names and four-space for the descriptions.
Done like that. I forgot to credit you with the idea in the commit log;
sorry about that.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fabien COELHO | 2017-09-05 15:11:18 | Re: pgbench: Skipping the creating primary keys after initialization |
| Previous Message | Tom Lane | 2017-09-05 14:52:47 | Re: Variable substitution in psql backtick expansion |