| From: | Mark Kirkwood <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz> |
|---|---|
| To: | Chris Pacejo <cpacejo(at)clearskydata(dot)com> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: Missing PRIMARY KEYs and duplicated rows |
| Date: | 2017-04-12 22:31:36 |
| Message-ID: | 74cccd1a-0db6-d0e1-5ae9-6c671d6285a6@catalyst.net.nz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 13/04/17 10:22, Chris Pacejo wrote:
> On Apr 12, 2017 6:13 PM, "Mark Kirkwood"
> <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz <mailto:mark(dot)kirkwood(at)catalyst(dot)net(dot)nz>>
> wrote:
>
>
> I'd be inclined to suspect the hardware with weird behaviour like
> that (memory and disk errors in particular).
>
>
>
> Me too, but how would that explain the observation that it's occurring
> only within one database (and on all tables within that database)? The
> only thing all tables within a database have in common on disk is that
> they reside in the same directory.
>
> And the ctids of the duplicate rows indicate that they're allocated
> sequentially in the same page as the legitimate rows. (The tables are
> mostly all less than a dozen rows.) How could this be explained by
> disk corruption?
>
> I suppose memory corruption is possible, but it still seems oddly
> specific.
Things disappearing and coming back sounds more like bad memory to as
well. I'd recommend taking that server down and running memcheck.
regards
Mark
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chris Pacejo | 2017-04-12 23:58:57 | Re: Missing PRIMARY KEYs and duplicated rows |
| Previous Message | Chris Pacejo | 2017-04-12 22:22:24 | Re: Missing PRIMARY KEYs and duplicated rows |