From: | Phil Hildebrand <phil(dot)hildebrand(at)moz(dot)com> |
---|---|
To: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> |
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:25:21 |
Message-ID: | CAKk9fdUZeSPf087SO9OOdn-vwbyfaUU78OCYqHiQDPO-93JdkQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Yeah - There's no sensitive data (it's public domain reviews).
I've attached the hexdump
On Mon, Dec 31, 2018 at 10:57 PM Andrew Gierth
<andrew(at)tao11(dot)riddles(dot)org(dot)uk> wrote:
>
> >>>>> "Phil" == Phil Hildebrand <phil(dot)hildebrand(at)moz(dot)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)
--
Phil Hildebrand
Sr. DBE @ Moz
206.696.3413
Attachment | Content-Type | Size |
---|---|---|
raw_hexdump.txt | text/plain | 37.1 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Gierth | 2019-01-01 07:57:04 | Re: BUG #15570: Vacuum analyze ERROR: MultiXactId XXXX has not been created yet -- apparent wraparound |
Previous Message | Andrew Gierth | 2019-01-01 06:56:58 | Re: BUG #15570: Vacuum analyze ERROR: MultiXactId XXXX has not been created yet -- apparent wraparound |