Re: Portal->commandTag as an enum

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 20:50:47
Message-ID: 20200211205047.GA6646@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2020-Feb-11, Mark Dilger wrote:

> I thought about generating the files rather than merely checking them.
> I could see arguments both ways. I wasn’t sure whether there would be
> broad support for having yet another perl script generating source
> files, nor for the maintenance burden of having to do that on all
> platforms. Having a perl script that merely sanity checks the source
> files has the advantage that there is no requirement for it to
> function on all platforms. There’s not even a requirement for it to
> be committed to the tree, since you could also argue that the
> maintenance burden of the script outweighs the burden of getting the
> source files right by hand.

No thanks.

--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Mark Dilger 2020-02-11 20:54:11 Re: Portal->commandTag as an enum
Previous Message Andres Freund 2020-02-11 20:46:38 Re: pg_locks display of speculative locks is bogus