| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Portal->commandTag as an enum |
| Date: | 2020-02-11 21:02:46 |
| Message-ID: | 20200211210246.GA1081@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2020-Feb-11, Mark Dilger wrote:
> > No thanks.
>
> I’m not sure which option you are voting for:
>
> (Option #1) Have the perl script generate the .c and .h file from a .dat file
>
> (Option #2) Have the perl script validate but not generate the .c and .h files
>
> (Option #3) Have no perl script, with all burden on the programmer to get the .c and .h files right by hand.
>
> I think you’re voting against #3, and I’m guessing you’re voting for #1, but I’m not certain.
I was voting against #2 (burden the programmer with consistency checks
that must be fixed by hand, without actually doing the programmatically-
doable work), but I don't like #3 either. I do like #1.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Dilger | 2020-02-11 21:05:12 | Re: Portal->commandTag as an enum |
| Previous Message | Mark Dilger | 2020-02-11 20:54:11 | Re: Portal->commandTag as an enum |