| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
| Cc: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, Dilip Kumar <dilipbalaut(at)gmail(dot)com>, vignesh C <vignesh21(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Reorderbuffer crash during recovery |
| Date: | 2019-11-07 16:31:23 |
| Message-ID: | 20191107163123.u5bi4f2rdbthj3rs@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
Hi,
On 2019-11-07 17:03:44 +0530, Amit Kapila wrote:
> On Thu, Nov 7, 2019 at 4:48 PM Tomas Vondra
> <tomas(dot)vondra(at)2ndquadrant(dot)com> wrote:
> >
> > I'm a bit confused - does this happen only with the logical_work_mem
> > patches, or with clean master too?
> >
>
> This occurs with the clean master. This is a base code problem
> revealed while doing stress testing of logical_work_mem patches.
As far as I can tell there are no repro steps included? Any chance to
get those?
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-11-07 16:35:55 | Re: BUG #16099: Segmentation fault with - triggers and procedures |
| Previous Message | Andres Freund | 2019-11-07 16:26:45 | Re: BUG #16099: Segmentation fault with - triggers and procedures |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Konstantin Knizhnik | 2019-11-07 16:32:44 | Re: [Proposal] Global temporary tables |
| Previous Message | Tom Lane | 2019-11-07 16:30:30 | Re: Keep compiler silence (clang 10, implicit conversion from 'long' to 'double' ) |