| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Isaac Morland <isaac(dot)morland(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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 14:06:29 |
| Message-ID: | CAFj8pRBBqCEFt3ScXvpx9zr-AZ8jY_vnUUu8bH5JGES0Nkws8Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
út 7. 4. 2020 v 12:49 odesílatel Isaac Morland <isaac(dot)morland(at)gmail(dot)com>
napsal:
> On Tue, 7 Apr 2020 at 03:30, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
> wrote:
>
>
>> your patch supports syntax
>>
>> (option1=value option2=value)
>>
>> It looks little bit inconsistent and unusual
>>
>>>
> It's the same as a connection string. Actually, maybe that's the key to
> allowing parentheses, etc. in option values if needed - allow the same
> single-quote quoting as in connection strings. Maybe even just call the
> same code to do the parsing.
>
I don't think so connection string syntax should be used there.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Julien Rouhaud | 2020-04-07 14:23:47 | Re: WAL usage calculation patch |
| Previous Message | Andrew Dunstan | 2020-04-07 13:42:09 | Re: backup manifests and contemporaneous buildfarm failures |