Skip site navigation (1) Skip section navigation (2)

Re: Dumping data using pg_dump after chrooting to a different partition

From: Krishnamurthy Radhakrishnan <kradhak(at)cisco(dot)com>
To: Craig Ringer <ringerc(at)ringerc(dot)id(dot)au>
Cc: Craig James <craig_james(at)emolecules(dot)com>, pgsql-admin(at)postgresql(dot)org
Subject: Re: Dumping data using pg_dump after chrooting to a different partition
Date: 2011-10-25 16:32:05
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-admin
Thanks. Using localhost instead of the actual host FQDN helped to fix 
the problem.

Thank you all for your help.


On 10/24/11 9:45 PM, Craig Ringer wrote:
> On 25/10/11 11:01, Krishnamurthy Radhakrishnan wrote:
>> Thanks Craig.
>> After configuring to accept TCP connections on port 5432, I tried to
>> specify the hostname as shown below and that didn't help. Is there
>> anything else that needs to be configured?
>> pg_dump -h -p 5432 -a -U postgres
>> pg_dump: [archiver (db)] connection to database "postgres" failed: could
>> not connect to server: Connection refused
>>      Is the server running on host "" and accepting
>>      TCP/IP connections on port 5432?
> Use "localhost" or "" if it's on the same machine to simplify
> things. If you try to connect to your host's public IP but
> postgresql.conf has listen_addresses='' or
> listen_addresses='localhost' then you won't be able to connect because
> Pg isn't listening on your public IP, only your loopback IP. A chroot
> won't affect tcp/ip, so it's still localhost when you're chrooted into
> another FS.
> Also, you may have firewall rules in place that prevent the connection,
> check for that.
> --
> Craig Ringer

In response to

pgsql-admin by date

Next:From: Adam DrayDate: 2011-10-25 18:01:50
Subject: Postgresql-contrib on RHEL6 x64 -- libpython2.4 dependency
Previous:From: Kevin GrittnerDate: 2011-10-25 14:41:53
Subject: Re: Create Temp tables on SLave

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group