Re: Another possible corruption bug in 9.3.2 or possibly a known MultiXact problem?

From: Greg Stark <stark(at)mit(dot)edu>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Andres Freund <andres(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Peter Geoghegan <pg(at)heroku(dot)com>
Subject: Re: Another possible corruption bug in 9.3.2 or possibly a known MultiXact problem?
Date: 2014-02-27 22:14:01
Message-ID: CAM-w4HOvoeu_v_nhmF+mqNH5nA7riQ0o53+6Qq+K=OL0Anumtg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Feb 27, 2014 at 2:34 PM, Alvaro Herrera
<alvherre(at)2ndquadrant(dot)com> wrote:
> Greg, Peter, if you could update your standbys to the current HEAD of
> REL9_3_STABLE for the affected apps and verify the problem no longer
> shows up in a reasonable timeframe, it would be great. (I'm assuming
> you saw this happen repeatedly.)

Actually I can do better. I restored the same base backup and applied
the same period of logs and can confirm that the rows in question now
appear normally:

=# select * from (select
(heap_page_items(get_raw_page('users',13065))).*) as x where lp
in(2,3,4,7);

lp | lp_off | lp_flags | lp_len | t_xmin | t_xmax | t_field3 |
t_ctid | t_infomask2 | t_infomask | t_hoff |
----+--------+----------+--------+---------+---------+----------+-----------+-------------+------------+--------+---
2 | 3424 | 1 | 232 | 5943845 | 728896 | 0 |
(13065,3) | 16416 | 4419 | 32 |
3 | 3152 | 1 | 272 | 5943849 | 5943879 | 0 |
(13065,4) | 49184 | 9475 | 32 |
4 | 2864 | 1 | 287 | 5943879 | 5943880 | 0 |
(13065,7) | 49184 | 9475 | 32 |
7 | 2576 | 1 | 287 | 5943880 | 0 | 0 |
(13065,7) | 32800 | 10499 | 32 |

--
greg

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2014-02-27 22:33:47 Re: UNION ALL on partitioned tables won't use indices.
Previous Message Alvaro Herrera 2014-02-27 22:04:07 Re: Backup throttling