Lou O'Quin wrote:

I can confirm this report. To fix it, you need to run 'gmake html'
twice, then the target PDF you want. This will all work automatically
in 8.3. Also, I assume it should be run against 8.2.1, not 8.2.

--
Bruce Momjian bruce@momjian.us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

PostgreSQL 8.2 U.S. documention (PDF) is missing the index contents.
(The index title is present, though.) The A4 version has the index
contents.

is missing the Index. the A4 version has an index, but the US version
(as of 1/10 1:00 PM MST) does not.

Lou O'Quin

Sr. Systems Analyst
Talley Defense Systems
Mesa, AZ
480.898.2385

This is automatically generated email about problems in a man page for which
you appear to be responsible. If you are not the right person or list, tell
me and I will attempt to correct my database.

See http://catb.org/~esr/doclifter/problems.html for details on how and
why these patches were generated. Feel free to email me with any questions.
Note: These patches do not change the mod date of any manual page. You
may wish to do that by hand.

Problems with vacuumdb.1:

1. Broken command synopsis syntax. This may mean you're using a
construction in the command synopsis other than the standard
[ ] | { }, or it may mean you have running text in the command synopsis
section (the latter is not technically an error, but it's impossible
to translate into DocBook markup).

Guillaume Lelarge lelarge.info> writes:

DateStyle and TimeZone have both historically been spelled like that,
and are delivered to client code in that form (not only in SHOW but
in the lower-level ParameterStatus message). I think the odds of
breaking client-side code are very high if we change it.

regards, tom lane

This is a multi-part message in MIME format.

Alvaro Herrera a ecrit le 22/12/2006 17:54:

Guillaume Lelarge wrote:

I checked the PDF available on
http://www.postgresql.org/files/documentation/pdf/8.2/postgresql-8.2-A4.pdf
and it does have the issues Guillaume mentions: table 8-13 (on page 105)
is certainly mangled (columns too wide), and table 8-18 is mangled too
(a row's content is too wide for the columns, so the text on one column
overlaps the text on the next). This problem can also be seen on other
tables, for example 9-5 and 9-6.

I printed one page and it looks just as silly, so it's not just a
display problem.

Also, the US version is lacking the index -- I suppose it was built
without the complete index.sgml file.

David Blewett dawninglight.net> writes:

I haven't gotten any reply from my posting to the upstream mailing list
at sourceforge :-( so it's hard to tell if anything will happen there.
I don't really approve of fixing this on a distro-by-distro basis, but
maybe we have no other choice.

Anyway, what I said to them was

------- Forwarded Message

Date: Sat, 09 Dec 2006 23:35:54 -0500
From: Tom Lane
To: openjade-devel@lists.sourceforge.net
Subject: Performance problems with NodeListObj lists

It's been folklore for some time at the PostgreSQL project
(www.postgresql.org) that running our documentation through jade to
produce TeX output requires about three days on current hardware :-(
Today I got motivated to look into why, and what I find is a pretty
localized problem, as illustrated by this oprofile trace:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

David Blewett wrote:

Hi Tom:

There's been a question posted to that bug. Would you mind replying
to it? You don't have to create an account there. I can post your reply.