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

Re: PostgreSQL 9.1 pg_dump setval() sets wrong value

From: Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com>
To: Greg Donald <gdonald(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: PostgreSQL 9.1 pg_dump setval() sets wrong value
Date: 2011-12-29 17:46:51
Message-ID: 4EFCA78B.3020703@gmail.com (view raw or flat)
Thread:
Lists: pgsql-general
On 12/29/2011 08:13 AM, Greg Donald wrote:
> On Wed, Dec 28, 2011 at 4:58 PM, Adrian Klaver<adrian(dot)klaver(at)gmail(dot)com>  wrote:
>> What is the pg_dump command, with options, you are using?
>
> My backup shell script contains:
>
> /usr/bin/pg_dump cp | bzip2>  $FILE

One possible issue that I see is the lack of explicit options. Given 
that you say you have two Postgres clusters on the machine it is 
entirely possible that the above command is picking up ENVIRONMENT 
variables that are pointing to a database different from the one you 
think. Try the command with explicit options, i.e. -p some_port -d 
database_name, that you know point to the database you want.

>
>


-- 
Adrian Klaver
adrian(dot)klaver(at)gmail(dot)com

In response to

pgsql-general by date

Next:From: Adrian KlaverDate: 2011-12-29 17:54:12
Subject: Re: PostgreSQL 9.1 pg_dump setval() sets wrong value
Previous:From: Merlin MoncureDate: 2011-12-29 17:19:13
Subject: Re: PostgreSQL 9.1 pg_dump setval() sets wrong value

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