On Sat, October 27, 2012 18:44, Tom Lane wrote: > "Erik Rijkers" <[email protected]> writes: >> [ LATERAL ] function_name ( [ argument [, ...] ] ) AS ( column_definition [, >> ...] ) > >> But what does 'column_definition' stand for? (These are the only >> occurrences of >> 'column_definition' in the manual.) > > This is the syntax for specifying what columns a > function-returning-RECORD is actually going to return. I'm too lazy to > chase down the reference and see whether it's really inconsistent or > not --- but that line was like that before I added [ LATERAL ] to it ... >
OK. I see it goes back to 7.3. It's probably not a problem. I returned to the initial reason that I looked at the select.sgml, namely the truncation of some of the synopsis-lines in the .pdf page for select.sgml. Attached patch wraps the worst-longest line so that if becomes visible in pdf. It makes the .html version slightly less pretty, but I hope the .pdf readability (integrity, even) counts for something too. (the remaining long lines in select.sgml page are cut off (for pdf) in the middle of some last element and as such are still readable / clear enough.) If changes like these (where the .html suffers slightly for .pdf integrity) are acceptable, I would like to make some more doc-patches where the .pdf is rendered readable (almost always the synopsis, but maybe there are still some code examples). Thanks, Erik Rijkers
select.sgml.diff
Description: Binary data
-- Sent via pgsql-docs mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs
