| From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: 10RC1 crash testing MultiXact oddity |
| Date: | 2017-09-22 19:39:36 |
| Message-ID: | CAMkU=1yW=BRJUaGMg64N4e5QkJv=u-hQXo6om85qQjFFtwnoLA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Sep 22, 2017 at 8:47 AM, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
wrote:
> Jeff Janes wrote:
> > I am running some crash recovery testing against 10rc1 by injecting torn
> > page writes, using a test case which generates a lot of multixact, some
> > naturally by doing a lot fk updates, but most artificially by calling
> > the pg_burn_multixact function from one of the attached patches.
>
> Is this new in pg10, or do you also see it in 9.6?
>
It turns out it is not new in pg10. I spotted in the log file only by
accident while looking for something else. Now that I am looking for it, I
do see it in 9.6 as well.
Cheers,
Jeff
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ashutosh Sharma | 2017-09-22 19:44:50 | Re: Page Scan Mode in Hash Index |
| Previous Message | Julien Rouhaud | 2017-09-22 19:34:11 | Re: [Proposal] Make the optimiser aware of partitions ordering |