Re: pg_dump vs pg_dumpall - small database cluster,

From: "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com>
To: "C(dot) Bensend" <benny(at)bennyvision(dot)com>
Cc: <pgsql-admin(at)postgresql(dot)org>
Subject: Re: pg_dump vs pg_dumpall - small database cluster,
Date: 2003-12-22 17:31:15
Message-ID: Pine.LNX.4.33.0312221030100.30417-100000@css120.ihs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Sat, 20 Dec 2003, C. Bensend wrote:

>
> >> pg_dumpall seems to do this for me, without any command-line args
> >> needed. Am I correct in saying that 'pg_dumpall > filename' will
> >> produce
> >> a PostgreSQL dump that includes _everything_ I need to go from a clean
> >> PG install to accepting connections again with data intact? Users,
> >> passwords, etc?
> >>
> >
> > and the owner of pg_dumpall process must be a database superuser.
>
> Absolutely... I'm running this directly on the database server, as the
> PostgreSQL superuser, so permissions aren't an issue. I just want to be
> very sure that pg_dumpall is getting absolutely everything I need,
> because I don't have the resources at this site to do full filesystem
> backups of this host.

Note that in the past, occasional dependency issues have cause pg_dumpall
to fail for certain users. I myself had it happen with a customer
sequence a little while ago on 7.2.4. Unfortunately, I'm unable to
reproduce the sequence of events that caused it, so I can't really report
it as a bug.

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Yuji Shinozaki 2003-12-22 20:17:02 Re: constaint addition to existing schema
Previous Message Jodi Kanter 2003-12-22 17:26:18 constaint addition to existing schema