Thread

1. BUG #1349: Gap in documentation - pg_dump

   PostgreSQL Bugs List <pgsql-bugs@postgresql.org> — 2004-12-16T08:16:56Z

   The following bug has been logged online:
   
   Bug reference:      1349
   Logged by:          PiotrL
   
   Email address:      vpiotr@poczta.onet.pl
   
   PostgreSQL version: 7.4.6
   
   Operating system:   Windows
   
   Description:        Gap in documentation - pg_dump
   
   Details: 
   
   I'm sorry, but I didn't found a better place to report that:
   
   There is no information how to specify user's password in pg_dump 
   documentation. I have spent half of day searching for that (pg_hba.conf was 
   not working for me) and the answer is very simple: 
   
   You can use SET variables for that:
   
   PGUSER=web-user
   PGPASSWORD=secret
   
   Please include that in pg_dump documentation.
   
   Regards,
   Piotr
    
   
   
   

2. Re: BUG #1349: Gap in documentation - pg_dump

   Bruno Wolff III <bruno@wolff.to> — 2004-12-16T13:44:07Z

   On Thu, Dec 16, 2004 at 08:16:56 +0000,
     PostgreSQL Bugs List <pgsql-bugs@postgresql.org> wrote:
   > 
   > I'm sorry, but I didn't found a better place to report that:
   > 
   > There is no information how to specify user's password in pg_dump 
   > documentation. I have spent half of day searching for that (pg_hba.conf was 
   > not working for me) and the answer is very simple: 
   > 
   > You can use SET variables for that:
   > 
   > PGUSER=web-user
   > PGPASSWORD=secret
   > 
   > Please include that in pg_dump documentation.
   
   You don't want to do that; on many systems the contents of environment
   variables are visible to other processes. You can keep a password in
   ~/.pgpass and that will work for more than just pg_dump. If the batch
   scripts are running on the same machine as the server, consider using
   ident authentication.
   
   

3. Re: BUG #1349: Gap in documentation - pg_dump

   Bruno Wolff III <bruno@wolff.to> — 2004-12-16T21:42:03Z

   On Thu, Dec 16, 2004 at 20:21:48 +0100,
     Piotr Likus <vpiotr@poczta.onet.pl> wrote:
   > 
   > Yes, maybe it is insecure, but sometimes "quick and dirty" solutions
   > are better than no solution at all.
   > After all you can add "not recommended" note to this tip.
   
   The official documentation isn't likely to be changed to instruct people
   how to incorrectly set up their system.
   
   It may be that there is a deficiency in the pg_dump documentation if you
   are expected to know something from another part of the manual that it
   may not be obvious that you should know. In that case the answer is
   to refer to the other section or to include enough information to
   avoid needing to refer to the other section.`