From: Tom Lane <tgl@sss.pgh.pa.us>
To: JTyrrell <jtyrrell_@hotmail.com>
Cc: pgsql-general@postgresql.org
Subject: Re: pg_dump problems
Date: Thu, 04 Jan 2007 13:39:11 -0500
Message-ID: <23142.1167935951@sss.pgh.pa.us> (raw)
In-Reply-To: <8156139.post@talk.nabble.com>
References: <8138723.post@talk.nabble.com>
<459BFD8D.4030100@archonet.com>
<8156139.post@talk.nabble.com>
JTyrrell <jtyrrell_@hotmail.com> writes:
> 1. pg_dump -s doesn't work. I've tried using a load of other options and
> none at all but no luck.
> 2. I'm running as root so wont be a problem there, and the file im dumping
> to has full permissions for everyone.
> What makes this even more confusing is I tried pg_dump with a database name
> that doesnt exist and tried dumping from database root with a user that
> doesn't have permission to do that. Both gave the same results as before.
> Its basically creating the file i need, looking for the database and not
> finding it. When you dump an empty database the file at least has some info
> on session authorization and the schema. Im getting nothing!
It's really hard to believe that pg_dump would write nothing to either
the output file or stderr. The only thought that comes to mind is that
if this machine has SELinux enabled, the SELinux policy might be
forbidding it from writing on the output file. What's the platform,
exactly?
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-general@postgresql.org
Cc: tgl@sss.pgh.pa.us, jtyrrell_@hotmail.com
Subject: Re: pg_dump problems
In-Reply-To: <23142.1167935951@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox