From: | kevin kempter <kevin(at)kevinkempterllc(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Dupes inserted that violate the PK |
Date: | 2008-07-08 17:04:01 |
Message-ID: | 65E0B7AA-6B04-4886-88DA-22ABDCA7D466@kevinkempterllc.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
8.2.9
I have a hunch what went wrong. We tested a warm standby failover
while the 'master' was still running - our warm standby includes a
process that grabs the final unarchived WAL segment from the master
pg_xlog directory. I have a hunch that this is where the disconnect
happened, I think the rule needs to be that we only execute a failover
based on bringing the master down as opposed to simply creating the
trigger file. I'm trying to test this theory out now - I'll update
the list with my findings.
/Kevin
On Jul 8, 2008, at 10:52 AM, Alvaro Herrera wrote:
> kevin kempter wrote:
>
>> We suspected the index was corrupt but a reindex fails for obvious
>> reasons.
>
> What version is this? We're investigating a similar problem on
> 8.1.11.
>
>
>
> --
> Alvaro Herrera http://www.CommandPrompt.com/
> PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | Igor Neyman | 2008-07-08 17:16:16 | Re: dropping a user in 8.2.6 |
Previous Message | Alvaro Herrera | 2008-07-08 16:52:29 | Re: Dupes inserted that violate the PK |