Skip site navigation (1) Skip section navigation (2)

Re: trouble with pg_dumpall

From: "Tena Sakai" <tsakai(at)gallo(dot)ucsf(dot)edu>
To: "Phillip Smith" <phillip(dot)smith(at)weatherbeeta(dot)com(dot)au>,<pgsql-admin(at)postgresql(dot)org>
Subject: Re: trouble with pg_dumpall
Date: 2008-02-28 01:40:47
Message-ID: FE44E0D7EAD2ED4BB2165071DB8E328C0378F0D3@egcrc-ex01.egcrc.org (view raw or flat)
Thread:
Lists: pgsql-admin
Hi Phillip,

Thank you for your suggestion.  So my script
file now looks like:

  #! /bin/bash

  PGUSER=postgres
  PGDATABASE=canon
  PGHOST=vixen
  PGPASSFILE=winkwink
  PGDATA=/usr/local/pgsql/data
  LD_LIBRARY_PATH=/usr/local/pgsql/lib
  export PGUSER PGDATABASE PGHOST PGPASSFILE PGDATA LD_LIBRARY_PATH
  # echo +++++++++
  # echo PGUSER: $PGUSER
  # echo PGDATABASE: $PGDATABASE
  # echo PGHOST: $PGHOST
  # echo PGPASSFILE: $PGPASSFILE
  # echo PGDATA: $PGDATA

  filename=`date +%G%m%d.%w`.gz
  /usr/local/pgsql/bin/pg_dumpall > $filename

and I still get the same output:

  Password:
  pg_dumpall: could not connect to database "template1": fe_sendauth: no password supplied

I just don't get it...

Tena Sakai
tsakai(at)gallo(dot)ucsf(dot)edu




-----Original Message-----
From: Phillip Smith [mailto:phillip(dot)smith(at)weatherbeeta(dot)com(dot)au]
Sent: Wed 2/27/2008 5:19 PM
To: Tena Sakai; pgsql-admin(at)postgresql(dot)org
Subject: RE: [ADMIN] trouble with pg_dumpall
 
Try explicitly setting those variables in your script:
	$PGUSER
	$PGDATABASE
	$PGHOST
	$PGPASSFILE
	$PGDATA


THINK BEFORE YOU PRINT - Save paper if you don't really need to print this

*******************Confidentiality and Privilege Notice*******************

The material contained in this message is privileged and confidential to
the addressee.  If you are not the addressee indicated in this message or
responsible for delivery of the message to such person, you may not copy
or deliver this message to anyone, and you should destroy it and kindly
notify the sender by reply email.

Information in this message that does not relate to the official business
of Weatherbeeta must be treated as neither given nor endorsed by Weatherbeeta.
Weatherbeeta, its employees, contractors or associates shall not be liable
for direct, indirect or consequential loss arising from transmission of this
message or any attachments
e-mail.

In response to

Responses

pgsql-admin by date

Next:From: Tena SakaiDate: 2008-02-28 02:26:54
Subject: Re: trouble with pg_dumpall
Previous:From: Phillip SmithDate: 2008-02-28 01:19:18
Subject: Re: trouble with pg_dumpall

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group