From: | Ivan Evtuhovich <evtuhovich(at)gmail(dot)com> |
---|---|
To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Two entries with the same primary key |
Date: | 2012-04-13 12:36:28 |
Message-ID: | CAOXtjwe89woSwHpBsy3z0mmNNGtFsVj3+frU_=eJ_RpD55j-xw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hello Merlin,
we've resynced slave and now everything is OK, thanks you for help.
And only one last question, where to read about this bug, because
my colleges want to know, what happens.
On Fri, Apr 13, 2012 at 00:48, Merlin Moncure <mmoncure(at)gmail(dot)com> wrote:
> On Thu, Apr 12, 2012 at 9:20 AM, Ivan Evtuhovich <evtuhovich(at)gmail(dot)com>
> wrote:
> > Hello,
> >
> > More then month ago we upgrade DB from 9.0 to 9.1 with pg_upgrade. Then
> we
> > move DB to another server with standard pg streaming replication.
> >
> > Now we have two entries with the same primary key. And I do not know
> what to
> > do.
> >
> > SELECT ctid, id from billing_invoices where id = 27362891;
> >
> > ctid | id
> > --------------+----------
> > (1112690,11) | 27362891
> > (1112438,26) | 27362891
> >
>
> Per some off-list conversation with Ivan, this is only happening on
> the standby. Ivan, what's the precise version of postgres you are
> using? When you first went to hs/sr? I bet your clog files are out
> of whack (and if so, probably upgrading to recent bugfix postgres and
> standby resync is the correct course of action).
>
> merlin
>
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Adams | 2012-04-13 12:41:39 | Updating pg_attribute to change field's data type from integer to bigint on very large table |
Previous Message | Dmitry E. Oboukhov | 2012-04-13 11:16:34 | aggregate arrays |