| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | "James Pang (chaolpan)" <chaolpan(at)cisco(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | "pgsql-performance(at)lists(dot)postgresql(dot)org" <pgsql-performance(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: thousands of CachedPlan entry per backend |
| Date: | 2023-06-01 12:48:23 |
| Message-ID: | 7bbe7bf1fa86dc075d2b655fdadd08fa99180212.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Thu, 2023-06-01 at 08:50 +0000, James Pang (chaolpan) wrote:
> we found thousands of cached plan , since JDBC driver only allow max 256 cached
> prepared statements, how backend cache so many sql plans. If we have one function,
> when application call that function will make backend to cache every SQL statement
> plan in that function too? and for table triggers, have similar caching behavior ?
Yes, as long as the functions are written in PL/pgSQL.
It only affects static SQL, that is, nothing that is run with EXECUTE.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sergio Rus | 2023-06-01 14:26:59 | Re: How to reduce latency with fast short queries in Postgresql 15.3 on a NUMA server |
| Previous Message | James Pang (chaolpan) | 2023-06-01 08:50:44 | RE: thousands of CachedPlan entry per backend |