Re: Another modest proposal for docs formatting: catalog descriptions

2020-05-10 Thread Tom Lane
Just FTR, here's a complete patch for this. 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 t

Re: Another modest proposal for docs formatting: catalog descriptions

2020-05-10 Thread Jonathan S. Katz
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

Remaining PDF layout issues

2020-05-10 Thread Tom Lane
There are something like 140 "exceeds the available area" PDF build warnings that will remain after the catalog-table reformatting I've proposed nearby. I've looked through these and they fall into two groups: 1. We have lots of overwidth examples. Using our standard monospaced font, A4-size pap

Getting rid of "Unresolved ID reference" in PDF builds

2020-05-10 Thread Tom Lane
Our PDF docs build has a couple of dozen complaints like WARNING: Destination: Unresolved ID reference "sql-altercollation-notes-title" found. These are due to cross-reference links like this: See below. They seem to render as desired, so it's not clear why we're getting the warnings, b

Re: 【memory barrier】Should we update the README.barrier description.

2020-05-10 Thread Simon Riggs
On Sun, 10 May 2020 at 02:01, postgresql_2...@163.com < postgresql_2...@163.com> wrote: > Hi > > When I read the introduction of Weaknesses of Memory Barriers in > README.barrier, the following maybe out-of-date now. > > Even very simple write operations often require additional synchronization. >