Re: [DOCS] [GENERAL] Password issue revisited
Tom Lane wrote: > "Michael Schmidt" <[EMAIL PROTECTED]> writes: > > ... Regarding how I concluded > > that PGPASSFILE was deprecated for pg_dump, I offer the following. > > > 1. The documentation for pg_dump in the manual (Section VI) includes a > > section labeled "Environment". This lists PGDATABASE, PGHOST, PGPORT, > > and PGUSER. It also says "default connection parameters" but there is > > no hyperlink or reference to another manual section to explain/define > > this term. > > Yeah. There is a link down in "See Also" but the incomplete > "Environment" section of these man pages seems misleading. > > Rather than try to maintain complete lists in each of the > client-application man pages, I propose we remove those sections > completely, and just rely on the See Also links to section 29.12. I think we can conclude that adding libpq in the "See Also" section of the documentation isn't sufficient. I have removed that mention, and added this text to the bottom of the "Environment" section for each utility: +This utility, like most other PostgreSQL utilities, +also uses the environment variables supported by . I have backpatched this to 8.2.X. -- Bruce Momjian <[EMAIL PROTECTED]> http://momjian.us EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + ---(end of broadcast)--- TIP 7: You can help support the PostgreSQL project by donating at http://www.postgresql.org/about/donate
[DOCS] should we have a separate page that clearly defines what a minor release is and why it's a good idea to keep up with them?
I know it's mentioned in the FAQ, but I'd like to have a separate page that describes what a minor release is, and why it's a good idea to keep up with them. Basically, I want something simple and clear to point middle-managers at when they ask me why I want to upgrade the database. I'm willing to write it, if there's a consensus that it would be worth having. Andrew ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [DOCS] should we have a separate page that clearly defines what a minor release is and why it's a good idea to keep up with them?
Andrew Hammond wrote: > I know it's mentioned in the FAQ, but I'd like to have a separate page > that describes what a minor release is, and why it's a good idea to > keep up with them. Basically, I want something simple and clear to > point middle-managers at when they ask me why I want to upgrade the > database. > > I'm willing to write it, if there's a consensus that it would be worth > having. I think adding to the FAQ is the best solution. What additional information to we need there? -- Bruce Momjian <[EMAIL PROTECTED]> http://momjian.us EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
