Re: BUG #17344: Assert failed on queiring async_capable foreign table with inheritance - Mailing list pgsql-bugs

From Etsuro Fujita
Subject Re: BUG #17344: Assert failed on queiring async_capable foreign table with inheritance
Date
Msg-id CAPmGK14UU-qKKHLhL4-rgxJg6zMtccbkj8diqSwX_o=hWdU1gA@mail.gmail.com
Whole thread Raw
In response to Re: BUG #17344: Assert failed on queiring async_capable foreign table with inheritance  (Alexander Lakhin <exclusion@gmail.com>)
Responses Re: BUG #17344: Assert failed on queiring async_capable foreign table with inheritance  (Alexander Lakhin <exclusion@gmail.com>)
List pgsql-bugs
Hi Alexander,

On Mon, Jan 3, 2022 at 4:00 AM Alexander Lakhin <exclusion@gmail.com> wrote:
> 31.12.2021 10:36, Etsuro Fujita wrote:
> > To fix, I modified postgresReScanForeignScan() so that we always
> > process a pending async request (if any) before restarting the foreign
> > scan.  Attached is a patch for that.  I tested the patch with the
> > first case, and it addresses the assertion failure.

> Thanks for the fix! I can confirm that it eliminates the failure and

Good to know.  Thanks for testing!

> propose a simple test case for the issue. Maybe you will find it useful.

Thanks, but in my environment, the test case doesn’t cause any
failure.  How about something like the attached, which is made by
modifying the original test case to avoid the connection-limit-error
issue.  In the attached, I also added a comment to a function to match
other places.

Best regards,
Etsuro Fujita

Attachment

pgsql-bugs by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: Possible bug report
Next
From: Etsuro Fujita
Date:
Subject: Re: BUG #17355: Server crashes on ExecReScanForeignScan in postgres_fdw when accessing foreign partition