| From: | Alexander Lakhin <exclusion(at)gmail(dot)com> |
|---|---|
| To: | Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)com>, Dmitry Dolgov <9erthalion6(at)gmail(dot)com> |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #17344: Assert failed on queiring async_capable foreign table with inheritance |
| Date: | 2022-01-02 19:00:00 |
| Message-ID: | d10cbf5d-d45a-d3b4-51b3-0a80f5039ed3@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Hello Etsuro-san,
31.12.2021 10:36, Etsuro Fujita wrote:
> On Tue, Dec 28, 2021 at 10:14 PM Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)com> wrote:
>> The root cause of the
>> assertion failure in the first case might be something other than the
>> limitation. I’ll look into this in more detail.
> 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
propose a simple test case for the issue. Maybe you will find it useful.
Best regards,
Alexander
| Attachment | Content-Type | Size |
|---|---|---|
| posgres_fdw.sql.patch | text/x-patch | 968 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2022-01-03 10:38:48 | BUG #17352: Column CHECK regex error |
| Previous Message | Tom Lane | 2022-01-01 21:27:05 | Re: BUG #17351: Altering a composite type created for a partitioned table can lead to a crash |