Thanks. Using localhost instead of the actual host FQDN helped to fix
the problem.
Thank you all for your help.
Radha
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 trie
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 bldr-ccm36.cisco.com -p 5432
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 bldr-ccm36.cisco.com -p 5432 -a -U postgres
pg_dump: [archiver (db)] connection to databas
On 10/24/11 3:10 PM, Krishnamurthy Radhakrishnan wrote:
Hi,
I am new to PostgreSQL. We are using PostgreSQL 9.0.2 on our linux server. We
have an instance of PostgreSQL 9.0 running using the primary partition on the
server.
We want to use the pg_dump and psql programs to migrate the data duri
Hi Kevin,
Can you please elaborate how to do the following?
connecting through a TCP connection and piping directly
from pg_dump to psql
Since we could have DB schema changes between the versions, we may not
be able to copy the data directory.
Does pg_upgrade support changes to the schema?
Krishnamurthy Radhakrishnan wrote:
> pg_dump works before chrooting to the secondary partition. Can
> you please provide a way to dump the data after chrooting?
How about connecting through a TCP connection and piping directly
from pg_dump to psql?
Of course, these days you have the option o
