| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | Daniel Verite <daniel(at)manitou-mail(dot)org>, Vik Fearing <vik(at)postgresfriends(dot)org>, Erik Rijkers <er(at)xs4all(dot)nl>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: proposal \gcsv |
| Date: | 2020-04-07 00:28:26 |
| Message-ID: | 1965.1586219306@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Here's a WIP patch for the parenthesized-options route.
I realized that if we make the options be single words in the form
name=value, we can easily handle the shortcut forms with no value.
So that's what this does.
What this does *not* do is offer any solution to the question of
how to put a right paren as the last character of a pset option
value. I don't really see any easy way to handle that, but maybe
we can punt for now.
Also no docs or test cases, but I see no point in putting effort into
that in advance of consensus that this is what we want.
0001 is some save/restore infrastructure that we'd need for pretty
much all of the proposals on the table, and then 0002 improves the
command itself.
regards, tom lane
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-pset-option-infrastructure-1.patch | text/x-diff | 7.6 KB |
| 0002-pset-options-for-slash-g-1.patch | text/x-diff | 4.6 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2020-04-07 00:35:02 | Re: FETCH FIRST clause WITH TIES option |
| Previous Message | Alexander Korotkov | 2020-04-07 00:25:47 | Re: [HACKERS] make async slave to wait for lsn to be replayed |