From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)anarazel(dot)de>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [COMMITTERS] pgsql: Add missing support for new node fields |
Date: | 2017-03-21 21:01:48 |
Message-ID: | alpine.DEB.2.20.1703212154420.22754@lancre |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
Hello Robert,
> IMHO, what would be a lot more useful than something that generates
> {read,equal,copy,out}funcs.c automatically would be something that
> just checks them for trivial errors of omission.
Hmmm. Checking for errors is actually more complicated than generating the
function: basically you have to generate the function, at least
implicitely, then parse the actual functions, then compare the two, then
generate meaningful messages. Thrice the work.
> The idea would be that if you added a field that wasn't supposed to be
> copied, you'd have to add something to copyfuncs.c that said, e.g.
>
> /* NOTCOPIED: mymember */
Yep, I was thinking of maybe use directives added to header files to
handle some special cases, but the real special cases would maybe more
readily turned to manual to keep a simpler generation script.
I do not fancy relying on another representation/language because of Tom's
objection that it would mean another language to learn, and I do not think
that it is desirable in pg.
--
Fabien.
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2017-03-22 02:12:01 | pgsql: doc: Update tool sets documentation for modern FreeBSD |
Previous Message | Fabien COELHO | 2017-03-21 20:50:45 | Re: [HACKERS] pgsql: Add missing support for new node fields |
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2017-03-21 21:03:16 | Re: Parallel tuplesort (for parallel B-Tree index creation) |
Previous Message | Fabien COELHO | 2017-03-21 20:50:45 | Re: [HACKERS] pgsql: Add missing support for new node fields |