Re: [DOCS] Building PDFs error: \pdfendlink ended up in different nesting level than \pd
Josh Kupershmidt writes: > Thanks for looking into this further. Both the -US and -A4 PDFs are > still failing for me on a recent git checkout including your change to > catalog.sgml. Hmph. HEAD does build both US and A4 sizes for me, using current Fedora 13 docs toolchain. But given what we now know, it could be sensitive to fairly small deltas in the toolchain, since any small change in spacing decisions might create or remove a problem. > I looked around line 1390679 of postgres-US.tex-pdf, where I saw this > snippet from seg.sgml: >(spaces around the range operator are ignored) Well, you're getting a lot further anyway ;-). But it's real curious that you seem to be hitting these more easily than anyone else ever has. I wonder if there's something about your toolchain that makes the issue more probable. Something we might consider doing to try to make this more stable is to see if we can force more page breaks in the PDF output. That would isolate each chapter or section from changes in others. regards, tom lane -- Sent via pgsql-docs mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs
Re: [DOCS] Building PDFs error: \pdfendlink ended up in different nesting level than \pd
I wrote: Josh Kupershmidt writes: >> I looked around line 1390679 of postgres-US.tex-pdf, where I saw this >> snippet from seg.sgml: >> (spaces around the range operator are ignored) The nearest preceding candidate for a split link seems to be the reference to table F-25 in the opening paragraph of section F.36.2 (attached PNG shows what it looks like when I build HEAD in US page size). Since that sentence is rather badly in need of copy-editing anyway, I'll go see if I can fix it. However, it's rather disturbing that in my build the problem seems to be more than half a dozen lines away from a page boundary. I could believe a line or two discrepancy between different toolchains, but this seems like a lot. > Something we might consider doing to try to make this more stable is to > see if we can force more page breaks in the PDF output. That would > isolate each chapter or section from changes in others. In my build, the entire contrib manual is potentially interdependent, because the sub-sections of Appendix F don't start new pages. This seems bad. What is even more curious is that it looks like the function "man pages" within the dblink section *do* get forced page breaks. That is inconsistent to say the least. How much control do we have over this type of formatting decision? regards, tom lane <> -- Sent via pgsql-docs mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs
Re: [DOCS] Problem with documentation of upgrades
Bruce Momjian wrote: > In looking over how upgrades are documented, it seems we talk about > dumping/reloading in two place in our documentation: > > Chapter 15. Installation from Source Code > 15.4. Upgrading > http://developer.postgresql.org/pgdocs/postgres/install-upgrading.html > > and: > > Chapter 24. Backup and Restore > 24.4. Migration Between Releases > http://developer.postgresql.org/pgdocs/postgres/migration.html > > The steps listed also use slightly different syntax, e.g. psql [-d], and > we call one "migrating" and the other "upgrading". > > This really needs a cleanup. Any suggestions? I feel the two sections > really need to be merged. Where should the combined section be placed? I went ahead and merged those two sections and put it in: Chapter 17. Server Setup and Operation 17.6. Upgrading a PostgreSQL Cluster 17.6.1. Upgrading Data via pg_dump 17.6.2. Other data migration methods You can view the result here: http://momjian.us/expire/pgsql.docs/upgrading.html There seemed to be continual confusion over whether you need to dump/reload, and I think it was because our upgrade instructions were duplicative and not complete in both places. This should solve the problem once and for all. -- Bruce Momjian http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. + -- Sent via pgsql-docs mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs
