| From: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, pgsql-docs(at)lists(dot)postgresql(dot)org, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Another modest proposal for docs formatting: catalog descriptions |
| Date: | 2020-05-10 18:03:32 |
| Message-ID: | 8cfed3a2-0850-6aca-8771-3c50dfb651b4@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-hackers |
On 5/10/20 12:27 PM, Tom Lane wrote:
> Just FTR, here's a complete patch for this.
Cool. I'll play around with it tonight once I clear out release work.
Per upthread reference, I believe you've become a CSS maven yourself.
> I successfully regenerated
> the column names, types, and ordering from the system catalogs, and
> plugged the descriptions back into that by dint of parsing them out of
> the XML. The "references" data was based on findoidjoins' results plus
> hand additions to cover all the cases we are calling out now (there are
> a lot of "references" links for attnums and a few other non-OID columns,
> plus references links for views which findoidjoins doesn't consider).
> So I have pretty high confidence that this info is OK. I'd be too
> embarrassed to show anybody the code though ;-) ... it was just a brute
> force hack.
If it works it works ;)
Jonathan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-05-10 21:31:20 | Remaining PDF layout issues |
| Previous Message | Tom Lane | 2020-05-10 16:27:23 | Re: Another modest proposal for docs formatting: catalog descriptions |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-05-10 19:07:17 | Re: Back-branch minor release notes are up for review |
| Previous Message | Dmitry Dolgov | 2020-05-10 17:49:35 | Re: Index Skip Scan |