On Fri, Apr 13, 2012 at 7:36 AM, Ivan Evtuhovich wrote:
> 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.
there are several standby related issues
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 wrote:
> On Thu, Apr 12, 2012 at 9:20 AM, Ivan Evtuhovich
Hi,
our current version both on master and slave is
PostgreSQL 9.1.3 on x86_64-pc-linux-gnu, compiled by gcc-4.4.real (Debian
4.4.5-8) 4.4.5, 64-bit
But as i remember, we start streaming replication on 9.1.2 and then upgrade
to 9.1.3. My ops now on vacations, and we will make standby resync
on Mo
On Thu, Apr 12, 2012 at 9:20 AM, Ivan Evtuhovich 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.
On Thu, Apr 12, 2012 at 9:20 AM, Ivan Evtuhovich 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.
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;
cti
