Re: [DOCS] Outdated note
Alvaro Herrera <[EMAIL PROTECTED]> writes: > On 4.1.2.1. String Constants, the following note appears: > Note: While ordinary strings now support C-style backslash escapes, > future versions will generate warnings for such usage and eventually > treat backslashes as literal characters to be standard-conforming. > That future version is 8.2, so the note should be updated to reflect it. Done; I ended up rewriting the whole subsection. I notice though that the following subsection about dollar quoting could really do with some rework too, because it implicitly assumes that backslashes are special in ordinary string literals. The example it gives to show the usefulness of dollar quoting for nested literals is really not very compelling at all if backslashes aren't special :-(. Can anyone come up with a better example that depends only on avoiding multiplied single quotes? regards, tom lane ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [DOCS] Empty index in A4 version of 8.1 PDF documentation
Benno Puetz wrote: > I just downloaded the current documentation PDFs and found that the A4 > version has no index whereas the US version does ... That's probably because the A4 version got generated first and created the index entries file as part of the process, while the Letter version was able to reuse the file from the A4 run. It would be neat to have some Makefile trickery to be able to detect that the just-finished run was done without an index entries file and and repeat the process in that case. -- Alvaro Herrerahttp://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
[DOCS] "Fast Forward" links don't seem to be correct
If you go to a regular, non-chapter-heading page in the PG docs, such as http://developer.postgresql.org/pgdocs/postgres/extend-type-system.html and try the "Fast Backward" link, it goes to that chapter's heading page, which seems reasonable. But the "Fast Forward" link points to the same place. Shouldn't it lead to the *next* chapter, instead? This seems to be the case not only in HEAD, but for all the on-line release versions since 7.4 (the first to have these links). regards, tom lane ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [DOCS] Empty index in A4 version of 8.1 PDF documentation
Alvaro Herrera wrote: > That's probably because the A4 version got generated first and > created the index entries file as part of the process, while the > Letter version was able to reuse the file from the A4 run. The index entries are only generated as a side effect of HTML builds. -- Peter Eisentraut http://developer.postgresql.org/~petere/ ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [DOCS] Empty index in A4 version of 8.1 PDF documentation
Alvaro Herrera <[EMAIL PROTECTED]> writes: > It would be neat to have some Makefile trickery to be able to detect > that the just-finished run was done without an index entries file and > and repeat the process in that case. [ shrug... ] The standard solution is to run the build twice, no matter what. You have no way to be sure the existing index file is correct even if it's present... regards, tom lane ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
