| From: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> |
|---|---|
| To: | Phil Hildebrand <phil(dot)hildebrand(at)moz(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #15570: Vacuum analyze ERROR: MultiXactId XXXX has not been created yet -- apparent wraparound |
| Date: | 2019-01-01 07:57:04 |
| Message-ID: | 87imz8stsw.fsf@news-spur.riddles.org.uk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
>>>>> "Phil" == Phil Hildebrand <phil(dot)hildebrand(at)moz(dot)com> writes:
Phil> Yeah - There's no sensitive data (it's public domain reviews).
Phil> I've attached the hexdump
OK. The page is definitely corrupt starting at offset 0x1000 (i.e.
offset 4kB in the 8kB page), but it's harder than usual to spot because
(a) the tear is in the middle of a text field and (b) the data in the
second half of the page is actually from a page of what is presumably a
different partition of the same table (it has the same row structure,
but the data is from 2017 not 2018).
The split being on a 4k boundary points the finger at the hardware or
OS, since pg doesn't care about 4k hardware pages or 4k disk sectors but
rather does everything in 8k blocks.
--
Andrew.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Phil Hildebrand | 2019-01-01 08:13:05 | Re: BUG #15570: Vacuum analyze ERROR: MultiXactId XXXX has not been created yet -- apparent wraparound |
| Previous Message | Phil Hildebrand | 2019-01-01 07:25:21 | Re: BUG #15570: Vacuum analyze ERROR: MultiXactId XXXX has not been created yet -- apparent wraparound |