From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Hao Lee <mixtrue(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Do we need use more meaningful variables to replace 0 in catalog head files? |
Date: | 2016-11-09 04:44:22 |
Message-ID: | 14521.1478666662@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> Most of these files don't have that many entries, and they're not
> modified that often. The elephant in the room is pg_proc.h, which is
> huge, frequently-modified, and hard to decipher. But I think that's
> going to need more surgery than just introducing named constants -
> which would also have the downside of making the already-long lines
> even longer.
I don't think we need "named constants", especially not
manually-maintained ones. The thing that would help in pg_proc.h is for
numeric type OIDs to be replaced by type names. We talked awhile back
about introducing some sort of preprocessing step that would allow doing
that --- ie, it would look into some precursor file for pg_type.h and
extract the appropriate OID automatically. I'm too tired to go find the
thread right now, but it was mostly about building the long-DATA-lines
representation from something easier to edit.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2016-11-09 05:01:07 | Re: Dumb mistakes in WalSndWriteData() |
Previous Message | Tom Lane | 2016-11-09 03:47:34 | Re: WIP: About CMake v2 |