| From: | Joel Jacobson <joel(at)trustly(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Rework the way multixact truncations work |
| Date: | 2015-09-29 11:54:12 |
| Message-ID: | CAASwCXf_Ho2W6=oBwKbW8BwTQMF1LeeaGg2Y_cv94kwXWP79rg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Sep 22, 2015 at 3:20 PM, Andres Freund <andres(at)anarazel(dot)de> wrote:
> What I've tested is the following:
> * continous burning of multis, both triggered via members and offsets
> * a standby keeping up when the primary is old
> * a standby keeping up when the primary is new
> * basebackups made while a new primary is under load
> * verified that we properly PANIC when a truncation record is replayed
> in an old standby.
Are these test scripts available somewhere?
I understand they might be undocumented and perhaps tricky to set it all up,
but I would be very interested in them anyway,
think you could push them somewhere?
Thanks a lot for working on this!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stanislav Kelvich | 2015-09-29 11:56:04 | Box type equality |
| Previous Message | Robert Haas | 2015-09-29 11:53:53 | Re: Rework the way multixact truncations work |