| From: | Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> |
|---|---|
| To: | Amit Langote <amitlangote09(at)gmail(dot)com> |
| Cc: | Tender Wang <tndrwang(at)gmail(dot)com>, David Rowley <dgrowleyml(at)gmail(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org, tharakan(at)gmail(dot)com |
| Subject: | Re: BUG #18830: ExecInitMerge Segfault on MERGE |
| Date: | 2025-03-13 14:42:10 |
| Message-ID: | CAEZATCX4owkQv7NE02hModeCE48DUa+VzYHckx=iEntjrOAL8w@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Thu, 13 Mar 2025 at 12:44, Amit Langote <amitlangote09(at)gmail(dot)com> wrote:
>
> One thing I'd like to avoid is taking any locks during ExecInitNode(),
> including in functions like ExecGetRangeTableRelation(). Doing so
> would require checking whether the CachedPlan is still valid and
> handling invalidation if it isn't -- see commit 525392d5727f for
> background.
>
Yes, I wondered about that. I saw that earlier commit, and the notes
in the executor README, but I still don't quite understand.
Specifically, how is locking this pruned leaf partition in
ExecInitModifyTable() different from locking any other pruned leaf
partition later in the INSERT path? (For example, as part of an UPDATE
that moves a tuple from an unpruned partition to a pruned one.)
Regards,
Dean
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2025-03-13 14:43:04 | Re: BUG #18843: ERROR: Input of anonymous composite types is not implemented in array_agg function |
| Previous Message | Amit Langote | 2025-03-13 12:44:44 | Re: BUG #18830: ExecInitMerge Segfault on MERGE |