| From: | Chris Pacejo <cpacejo(at)clearskydata(dot)com> |
|---|---|
| To: | Mark Kirkwood <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: Missing PRIMARY KEYs and duplicated rows |
| Date: | 2017-04-12 22:22:24 |
| Message-ID: | CAC8iE5iXZauGLC3eBWKHHGSWFsP2W1BsRnP789AjaRFY2pGEdQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Apr 12, 2017 6:13 PM, "Mark Kirkwood" <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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Kirkwood | 2017-04-12 22:31:36 | Re: Missing PRIMARY KEYs and duplicated rows |
| Previous Message | Mark Kirkwood | 2017-04-12 22:13:30 | Re: Missing PRIMARY KEYs and duplicated rows |