On Thu, Jun 1, 2023 at 4:51 AM James Pang (chaolpan)
wrote:
> 2) from this line, we saw total 42 blocks ,215 chunks
> CacheMemoryContext: 8737352 total in 42 blocks; 1021944 free (215 chunks);
> 7715408 used,
>
> But from sum of it’s child level entrys, total sum(child lines)
> block ,t
, June 1, 2023 8:48 PM
To: James Pang (chaolpan) mailto:[email protected]>>;
Pavel Stehule mailto:[email protected]>>
Cc:
[email protected]<mailto:[email protected]>
Subject: Re: thousands of CachedPlan entry per backend
On Thu, 2023
023 8:48 PM
> To: James Pang (chaolpan) ; Pavel Stehule <
> [email protected]>
> Cc: [email protected]
> Subject: Re: thousands of CachedPlan entry per backend
>
> On Thu, 2023-06-01 at 08:50 +, James Pang (chaolpan) wrote:
> > we found
James Pang (chaolpan) ; Pavel Stehule
Cc: [email protected]
Subject: Re: thousands of CachedPlan entry per backend
On Thu, 2023-06-01 at 08:50 +, James Pang (chaolpan) wrote:
> we found thousands of cached plan , since JDBC driver only allow max
> 256 cached prepared
On Thu, 2023-06-01 at 08:50 +, 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 cac
PM
To: Laurenz Albe
Cc: James Pang (chaolpan) ;
[email protected]
Subject: Re: thousands of CachedPlan entry per backend
Hi
čt 1. 6. 2023 v 8:53 odesílatel Laurenz Albe
mailto:[email protected]>> napsal:
On Thu, 2023-06-01 at 03:36 +, James Pang (chaolpan)
Hi
čt 1. 6. 2023 v 8:53 odesílatel Laurenz Albe
napsal:
> On Thu, 2023-06-01 at 03:36 +, James Pang (chaolpan) wrote:
> > PG V14.8-1 , client using Postgresql JDBC driver we found 40MB process
> memory per
> > backend, from Operating system and memorycontext dump “Grand total:”,
> both mache
On Thu, 2023-06-01 at 03:36 +, James Pang (chaolpan) wrote:
> PG V14.8-1 , client using Postgresql JDBC driver we found 40MB process memory
> per
> backend, from Operating system and memorycontext dump “Grand total:”, both
> mached.
> But from details, we found almost of entry belong to “Cac
