| From: | Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)com> |
|---|---|
| To: | Richard Guo <guofenglinux(at)gmail(dot)com> |
| Cc: | tharakan(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #17713: Assert with postgres_fdw in v12 |
| Date: | 2022-12-15 12:33:31 |
| Message-ID: | CAPmGK149-HxDEviFGEyGWG2U9+BRPnYpHYDZbHrF5104vmza1Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Wed, Dec 14, 2022 at 7:02 PM Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)com> wrote:
> On Tue, Dec 13, 2022 at 12:20 PM Richard Guo <guofenglinux(at)gmail(dot)com> wrote:
> > On Mon, Dec 12, 2022 at 7:10 PM PG Bug reporting form <noreply(at)postgresql(dot)org> wrote:
> >> This is a repro that triggers an assert (only) in REL_12_STABLE. In
> >> particular the issue seems to have begun after this commit -
> >> 08d2d58a2a1c8ef8d39e8132d39ee14a1d029500. The foreign table
> >> is empty so am unsure if Assert()'s expectations are valid.
> >>
> >> Since all versions v13+ seem to work okay, it is possible that a future
> >> bug-fix was not backpatched far enough to v12.
> >
> > Yes, I think it is 5e7fa189e, which should be back-patched to v12.
> Will back-patch to v12 as well.
Done.
Best regards,
Etsuro Fujita
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Gustafsson | 2022-12-15 13:18:05 | Re: BUG #17720: pg_dump creates a dump with primary key that cannot be restored, when specifying 'using index ...' |
| Previous Message | niraj nandane | 2022-12-15 09:33:28 | pg_rewind succeed but postgresql showing error when trying to make standby with common ancestor |