| From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
|---|---|
| To: | PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | pgbench - allow backslash-continuations in custom scripts |
| Date: | 2015-05-14 16:10:12 |
| Message-ID: | alpine.DEB.2.10.1505141510130.1821@sto |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Add backslash continuations to pgbench custom scripts.
The benefit of this approach is that it is upward compatible, and it is
also pretty simple to implement. The downside is that backslash
continuation is not the best syntax ever invented, but then you do not
have to use it if you do not like it.
The alternative would be to make semi-colon a mandatory end-of-line
marker, which would introduce an incompatibility and requires more efforts
to implement, including some kind of SQL-compatible lexer.
IMHO this approach is the best compromise.
--
Fabien.
| Attachment | Content-Type | Size |
|---|---|---|
| pgbench-conts-1.patch | text/x-diff | 2.6 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2015-05-14 16:10:32 | Re: pgsql: Add pg_audit, an auditing extension |
| Previous Message | Alvaro Herrera | 2015-05-14 16:01:47 | Re: [COMMITTERS] pgsql: Add pg_audit, an auditing extension |