On Thu, Jan 27, 2011 at 6:57 PM, Tom Lane wrote:
> Josh Kupershmidt writes:
>> How did you figure out that the problem was coming from that spot in
>> installation.sgml? I'd be interested to see whether another hack would
>> work in lieu of an actual fix in pdftex.
>
> If you look at the mentione
I have created the attached patch which rewords the mention of
pg_upgrade in the docs. I think it is clearer and more concise. Should
we mention that people should have a recent pg_dump? If so, that should
be in the pg_upgrade man page, not here.
--
Bruce Momjian http://momjian.us
Thom Brown wrote:
> On 28 January 2011 02:35, Bruce Momjian wrote:
> > There has been discussion about how hard it is to navigate our
> > documentation, particularly the lack of an "Up" link at the top of the
> > page, and uselessness of the "fast forward/backward" links.
> >
> > Who is going to c
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 2
Alvaro Herrera writes:
> Excerpts from Tom Lane's message of jue ene 27 20:57:27 -0300 2011:
>> (Note: if you just do "make postgres-A4.pdf", make will unhelpfully
>> throw away the tex-pdf intermediate file upon error. What I have done
>> when I needed to look is to explicitly "make postgres-A4.
In looking over the documentation, I found many places where we were not
capitalizing all the appropriate words in a title, and only capitalizing
the first word.
The attached diff adds proper capitalization for all our documentation
titles. You can also view it on github:
https://github.
Excerpts from Tom Lane's message of jue ene 27 20:57:27 -0300 2011:
> http://tug.org/errors.html
> explains that this error message occurs when a hyperlink would get split
> across a page boundary in the PDF output. The recommended solution is
> to adjust your text to prevent the link from being
On 28 January 2011 02:35, Bruce Momjian wrote:
> There has been discussion about how hard it is to navigate our
> documentation, particularly the lack of an "Up" link at the top of the
> page, and uselessness of the "fast forward/backward" links.
>
> Who is going to correct this? Should I do it?
There has been discussion about how hard it is to navigate our
documentation, particularly the lack of an "Up" link at the top of the
page, and uselessness of the "fast forward/backward" links.
Who is going to correct this? Should I do it? Where should I look?
--
Bruce Momjian http:
Josh Kupershmidt writes:
> On Wed, Jan 26, 2011 at 11:27 AM, Tom Lane wrote:
>> Josh Kupershmidt writes:
>>> though after a few minutes, I get problems from pdfTeX:
>>> [snip]
>>> ! pdfTeX error (ext4): \pdfendlink ended up in different nesting level than
>>> \pdfstartlink.
>> We've seen cases
10 matches
Mail list logo