From: | Hunter Hillegas <lists(at)lastonepicked(dot)com> |
---|---|
To: | PostgreSQL <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: 7.4 Crashed... Why? |
Date: | 2003-12-07 02:49:30 |
Message-ID: | BBF7D53A.E7E7A%lists@lastonepicked.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Verified that no shell startup scripts are running... And the backup
proceeded normally last night with no crash.
I'm starting to think that I'm not going to be able to track this down and
have to hope it doesn't happen again.
> From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
> Date: Sat, 06 Dec 2003 20:36:39 -0500
> To: Hunter Hillegas <lists(at)lastonepicked(dot)com>
> Cc: PostgreSQL <pgsql-general(at)postgresql(dot)org>
> Subject: Re: [GENERAL] 7.4 Crashed... Why?
>
> Hunter Hillegas <lists(at)lastonepicked(dot)com> writes:
>> I did find a cron job that was running in the suspect time... But all it
>> does is the following:
>> DATE=`date +%Y%m%d`
>> DB1=/root/database_backup/db1_db.$DATE
>> su - postgres -c "/usr/local/pgsql/bin/pg_dump db1" >> $DB1
>> gzip $DB1
>> Is it possible this could cause some strange behavior? This backup script
>> has been running for a year (every night) w/o any trouble.
>
> The cron script itself certainly looks unexceptional. But if "su - postgres"
> executes postgres' ~/.profile or other shell-startup scripts (I think it
> does so on some platforms but not others), maybe you had some weird
> behavior recently added to those scripts?
>
> regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2003-12-07 03:36:14 | Re: IDENT and IPv6 (was Re: [GENERAL] pg_hba.conf |
Previous Message | Tom Lane | 2003-12-07 01:36:39 | Re: 7.4 Crashed... Why? |