Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id B41749FA249 for ; Fri, 5 Jan 2007 05:16:49 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-new, port 10024) with ESMTP id 16884-09 for ; Fri, 5 Jan 2007 05:16:13 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from talk.nabble.com (www.nabble.com [72.21.53.35]) by postgresql.org (Postfix) with ESMTP id 188919FA0B7 for ; Fri, 5 Jan 2007 05:16:16 -0400 (AST) Received: from [72.21.53.38] (helo=jubjub.nabble.com) by talk.nabble.com with esmtp (Exim 4.50) id 1H2lBP-0001KA-0n for pgsql-general@postgresql.org; Fri, 05 Jan 2007 01:16:15 -0800 Message-ID: <8175027.post@talk.nabble.com> Date: Fri, 5 Jan 2007 01:16:14 -0800 (PST) From: JTyrrell To: pgsql-general@postgresql.org Subject: Re: pg_dump problems In-Reply-To: <23142.1167935951@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: jtyrrell_@hotmail.com References: <8138723.post@talk.nabble.com> <459BFD8D.4030100@archonet.com> <8156139.post@talk.nabble.com> <23142.1167935951@sss.pgh.pa.us> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=1.201 tagged_above=0 required=5 tests=AWL, BAYES_40, FORGED_HOTMAIL_RCVD2 X-Spam-Level: * X-Archive-Number: 200701/181 X-Sequence-Number: 106721 Im using Red Hat Enterprise Linux 4. Thing is it worked before christmas but doesn't now. I've just moved the data across by hand so its not too much of a problem anymore. Might need to use dump again though so would be nice to get the problem fixed Tom Lane-2 wrote: > > JTyrrell 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 > > ---------------------------(end of broadcast)--------------------------- > TIP 4: Have you searched our list archives? > > http://archives.postgresql.org/ > > -- View this message in context: http://www.nabble.com/pg_dump-problems-tf2912789.html#a8175027 Sent from the PostgreSQL - general mailing list archive at Nabble.com.