| From: | Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Richard Guo <guofenglinux(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Oversight in reparameterize_path_by_child leading to executor crash |
| Date: | 2023-08-03 04:38:39 |
| Message-ID: | CAExHW5viSrPBOdMpAQ7h8DXDQEuvJevFV0CEF5w8ERw+bTz6sQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Aug 1, 2023 at 6:50 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Alternatively, could we postpone the reparameterization until
> createplan.c? Having to build reparameterized expressions we might
> not use seems expensive, and it would also contribute to the memory
> bloat being complained of in nearby threads.
>
As long as the translation happens only once, it should be fine. It's
the repeated translations which should be avoided.
--
Best Wishes,
Ashutosh Bapat
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Rowley | 2023-08-03 04:50:21 | Re: Fix incorrect start up costs for WindowAgg paths (bug #17862) |
| Previous Message | Peter Smith | 2023-08-03 04:05:11 | Re: [PATCH] Reuse Workers and Replication Slots during Logical Replication |