Re: Poll: are people okay with function/operator table redesign?
Alvaro Herrera <alvherre@2ndquadrant.com>
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Victor Yegorov <vyegorov@gmail.com>, PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>
Date: 2020-04-20T22:14:33Z
Lists: pgsql-hackers
On 2020-Apr-20, Tom Lane wrote: > Alvaro Herrera <alvherre@2ndquadrant.com> writes: > > There's one with a separate column for the operator, without types, at > > the left (the "with names" example at > > https://postgr.es/m/14380.1587242177@sss.pgh.pa.us ). That seemed > > pretty promising -- not sure why it was discarded. > > Well, I wouldn't say it was discarded --- but there sure wasn't > a groundswell of support. Ah. > Looking at it again, I'd be inclined not to bother with the > morerows trick but just to have an operator name entry in each row. > This table is a bit of an outlier anyway, I'm finding --- very few > of the operator tables have multiple entries per operator name. No disagreement here. 'morerows' attribs are always a messy business. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Commits
-
Doc: re-re-revise markup for tables of functions.
- 4ad047a6eac3 13.0 landed
-
Doc: revise formatting of function/operator tables.
- 737d69ffc3cf 13.0 landed