| From: | David Rowley <dgrowleyml(at)gmail(dot)com> |
|---|---|
| To: | Renan Alves Fonseca <renanfonseca(at)gmail(dot)com> |
| Cc: | Evgeny Morozov <postgresql4(at)realityexists(dot)net>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Querying one partition in a function takes locks on all partitions |
| Date: | 2025-03-31 03:10:21 |
| Message-ID: | CAApHDvp3EDrVhGjmb21bceJ5-Y7iXKOn2UGG3-ngp_9ob_mpLw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sat, 29 Mar 2025 at 10:30, Renan Alves Fonseca
<renanfonseca(at)gmail(dot)com> wrote:
> Currently, in the SQL function path the plan is always generic. The
> planner ignores the function arguments. The plan_cache_mode setting
> has no effect in this path.
>
> I agree that the docs should be more explicit about this. There is a
> high penalty for using generic plans in complex functions.
If you have any suggestions about where you think those should be
added or wording for that, please feel free to suggest.
For the part that's specific to partitioning, I've suggested some
additional wording in the relevant spot in [1].
David
[1] https://postgr.es/m/CAApHDvogvzANoTOCyXUWgEuPFx1nT6S63aAN0bDRSJ=TaGBWew@mail.gmail.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2025-03-31 03:21:53 | Re: Querying one partition in a function takes locks on all partitions |
| Previous Message | Adrian Klaver | 2025-03-29 15:09:11 | Re: Quesion about querying distributed databases |