Re: BUG #15570: Vacuum analyze ERROR: MultiXactId XXXX has not been created yet -- apparent wraparound
| От | Andrew Gierth |
|---|---|
| Тема | Re: BUG #15570: Vacuum analyze ERROR: MultiXactId XXXX has not been created yet -- apparent wraparound |
| Дата | |
| Msg-id | 87muoksx17.fsf@news-spur.riddles.org.uk обсуждение исходный текст |
| Ответ на | Re: BUG #15570: Vacuum analyze ERROR: MultiXactId XXXX has not beencreated yet -- apparent wraparound (Phil Hildebrand <phil.hildebrand@moz.com>) |
| Ответы |
Re: BUG #15570: Vacuum analyze ERROR: MultiXactId XXXX has not beencreated yet -- apparent wraparound
|
| Список | pgsql-bugs |
>>>>> "Phil" == Phil Hildebrand <phil.hildebrand@moz.com> writes:
Phil> Sure - beacon=# select lp, lp_flags, t_xmin, t_xmax, t_field3,
Phil> t_ctid, beacon-# to_hex(t_infomask) as infomask,
Phil> to_hex(t_infomask2) as infomask2 beacon-# from
Phil> heap_page_items(get_raw_page('reviews_2018', 382604)) h;
This data page has obviously been partially overwritten by unrelated
data. (Notice that many of those numbers in the output correspond to
printable ASCII strings.)
A hexdump of the raw page will probably make it easy to see which part
is corrupt and what the offending data is. Something like this is
probably the easiest way to get it (adding any other required psql
options of course):
psql -d beacon -AXqt -c "select get_raw_page('reviews_2018', 382604)" |
perl -ne '/\\x([[:xdigit:]]+)/ and print pack("H*",$1)' |
hexdump -C
Assuming that doesn't reveal any sensitive data, can you send the output
of that?
--
Andrew (irc:RhodiumToad)
В списке pgsql-bugs по дате отправления: