Re: One DB not backed up by pg_dumpall

From: Francisco Reyes <lists(at)stringsutils(dot)com>
To: Michael Fuhr <mike(at)fuhr(dot)org>
Cc: PostgreSQL general <pgsql-general(at)postgresql(dot)org>
Subject: Re: One DB not backed up by pg_dumpall
Date: 2005-12-19 14:33:57
Message-ID: cone.1135002837.718731.87824.1000@zoraida.natserv.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Michael Fuhr writes:

> On Sun, Dec 18, 2005 at 11:29:13PM -0500, Francisco Reyes wrote:
>> Any reason why a database would not get dumped by pg_dumpall?
>> Always run pg_dumpall as the superuser.
>
> As the operating system superuser or as a database superuser?
> There's a difference.

As the database superuser.

> Is this a new procedure that has never worked, or is it an old
> procedure with a new problem?

Old procedure with a new problem.

> What are the exact commands you're using to dump and restore? Have
> you examined the output and the server's logs for errors and warnings?

The nightly script is:
#!/bin/csh
setenv PGUSER pgsql
setenv PGPASSWORD <password>
/usr/local/bin/pg_dumpall |/usr/bin/bzip2 -c ><file>

Where <file> is
/vol1/backs/pgsql/dump_all.sql.bz2

This procedure has been running for a while.
Last night before upgrading from 8.0.x to 8.1 I ran the script, then
proceeded to upgrade. So far from what I can tell only lost that one
database. :-(

However it deeply worries me. I will need to find if the script above is the
problem or something else. In coming days will keep an eye on the dump. This
one db I lost was bad to loose, but not critical (personal wiki), however it
would have been horrible if had lost other databases.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Francisco Reyes 2005-12-19 14:54:12 Re: One DB not backed up by pg_dumpall
Previous Message Chris Browne 2005-12-19 14:11:14 Re: out of memory during query execution