TECTED]
-Original Message-
From: Jeff Frost [mailto:[EMAIL PROTECTED]
Sent: Wed 2/27/2008 8:45 PM
To: Tena Sakai
Cc: pgsql-admin@postgresql.org
Subject: RE: [ADMIN] trouble with pg_dumpall
On Wed, 27 Feb 2008, Tena Sakai wrote:
> Hi Jeff,
>
>> What does your .pgpass l
> +
> PGUSER: postgres
> PGDATABASE: canon
> PGHOST: localhost
> PGPASSFILE: /usr/local/pgsql/.pgpass
> PGDATA: /usr/local/pgsql/data
> HOME: /usr/local/pgsql
> PATH:
/usr/local/pgsql/bin:/bin:/usr/kerberos/bin:/usr/local/java/bin:/usr/local/b
in:/bin:/usr/bin:/usr/X11R6/bin:/usr/local/ant/
-Original Message-
From: [EMAIL PROTECTED] on behalf of Phillip Smith
Sent: Wed 2/27/2008 8:31 PM
To: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] trouble with pg_dumpall
> -Original Message-
> From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Tena Sakai
> Sen
iginal Message-
From: Jeff Frost [mailto:[EMAIL PROTECTED]
Sent: Wed 2/27/2008 8:32 PM
To: Tena Sakai
Cc: pgsql-admin@postgresql.org
Subject: RE: [ADMIN] trouble with pg_dumpall
On Wed, 27 Feb 2008, Tena Sakai wrote:
Hi Jeff,
You cuaght me with a fine point.
but I didn't see HOME being ex
rom: Jeff Frost [mailto:[EMAIL PROTECTED]
Sent: Wed 2/27/2008 8:32 PM
To: Tena Sakai
Cc: pgsql-admin@postgresql.org
Subject: RE: [ADMIN] trouble with pg_dumpall
On Wed, 27 Feb 2008, Tena Sakai wrote:
> Hi Jeff,
>
> You cuaght me with a fine point.
>
>> but I didn't see HOME
On Wed, 27 Feb 2008, Tena Sakai wrote:
Hi Jeff,
You cuaght me with a fine point.
but I didn't see HOME being exported.
I have changed the script accordingly:
And the result/my claim remains the same as before:
pg_dumpall: could not connect to database "template1": fe_sendauth: no
passwo
> -Original Message-
> From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Tena Sakai
> Sent: Thursday, 28 February 2008 15:05
> To: Steve Holdoway; pgsql-admin@postgresql.org
> Subject: Re: [ADMIN] trouble with pg_dumpall
>
> As you can see, I am afraid
it
back to the way normally is (md5). I would rather
not do that and get .pgpass or PGPASSFILE to work
for me.
Regards,
Tena Sakai
[EMAIL PROTECTED]
-Original Message-
From: Jeff Frost [mailto:[EMAIL PROTECTED]
Sent: Wed 2/27/2008 7:41 PM
To: Tena Sakai
Cc: pgsql-admin@postgresql.o
.org
Subject: Re: [ADMIN] trouble with pg_dumpall
On Wed, 27 Feb 2008 17:12:40 -0800
"Tena Sakai" <[EMAIL PROTECTED]> wrote:
Here's your problem.
. .bashrc
You have an extremely minimal environment when running from cron, and you
certainly *aren't* running from th
n see, I am afraid my point still holds.
Regards,
Tena Sakai
[EMAIL PROTECTED]
-Original Message-
From: [EMAIL PROTECTED] on behalf of Steve Holdoway
Sent: Wed 2/27/2008 7:33 PM
To: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] trouble with pg_dumpall
On Wed, 27 Feb 2008 17:12:40
On Wed, 27 Feb 2008, Tena Sakai wrote:
Hi Jeff,
I bet the $HOME environment variable isn't
being set by your cron implementation.
Try putting an echo $HOME in your script and
see if it's defined.
I did. Here's the result:
+
PGUSER: postgres
PGDATABASE: canon
PGHOST: localhost
On Wed, 27 Feb 2008 17:12:40 -0800
"Tena Sakai" <[EMAIL PROTECTED]> wrote:
Here's your problem.
> . .bashrc
You have an extremely minimal environment when running from cron, and you
certainly *aren't* running from the home directory of the relevant user. You
need to set up your PATH and HOME
Regards,
Tena
-Original Message-
From: Jeff Frost [mailto:[EMAIL PROTECTED]
Sent: Wed 2/27/2008 6:59 PM
To: Tena Sakai
Cc: pgsql-admin@postgresql.org
Subject: RE: [ADMIN] trouble with pg_dumpall
On Wed, 27 Feb 2008, Tena Sakai wrote:
> Hi Jeff,
>
> Thanks for your reply, but
On Wed, 27 Feb 2008, Tena Sakai wrote:
I have turned every stone over and I am
pretty close to convince myself that the
way I am doing doesn't work. I can't
believe I am the one to discover such a
bug. I would love to hear somebody prove
me wrong.
But in the meantime, maybe I will take a
bit
On Wed, 27 Feb 2008, Tena Sakai wrote:
Hi Jeff,
Thanks for your reply, but I think you might
have missed an earlier thread. I am afraid
I have tried what you suggest. Below's my
previous post.
filename=`date +%G%m%d.%w`.gz
/usr/local/pgsql/bin/pg_dumpall > $filename
Here's what I get bac
IPv4 local connections:
host all all 127.0.0.1/32 md5
# IPv6 local connections:
hostall all ::1/128 md5
-Original Message-
From: [EMAIL PROTECTED] on behalf of Phillip Smith
Sent: Wed 2/27/2008 6:32 PM
To: pgsql-admin@postgresql.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 27 Feb 2008 18:26:54 -0800
"Tena Sakai" <[EMAIL PROTECTED]> wrote:
> But in the meantime, maybe I will take a
> bit different approach. Namely:
>
> Is there anyway I can pass the password to
> pg_dumpall via crontab?
You can use a pgpass f
Can you post your pg_hba.conf file to the list please?
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. I
have any suggestion in a
similar fashion.
I am all ears.
Regards,
Tena Sakai
[EMAIL PROTECTED]
-Original Message-
From: [EMAIL PROTECTED] on behalf of Tena Sakai
Sent: Wed 2/27/2008 5:40 PM
To: Phillip Smith; pgsql-admin@postgresql.org
Subject: Re: [ADMIN] trouble with pg_dumpall
Hi Phi
gresql.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
***
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***
Th
Hi Everybody,
I started running 8.3.0 recently on dell hardware
with redhat advanced server 4.
I have a problem with pg_dumpall via crontab.
I had a simple crontab to do the same thing on
8.2.4 and the same thing doesn't work.
Here's my very simple crontab entry:
xx xx * * * sh /usr/local/pgs
22 matches
Mail list logo
