| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Job <Job(at)colliniconsulting(dot)it> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: R: CachedPlan logs until full disk |
| Date: | 2016-12-02 15:10:05 |
| Message-ID: | 28330.1480691405@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Job <Job(at)colliniconsulting(dot)it> writes:
> Tonight this problem happened again:
> CachedPlan: 1024 total in 1 blocks; 640 free (0 chunks); 384 used
> CachedPlanSource: 1024 total in 1 blocks; 336 free (0 chunks); 688 used
> SPI Plan: 1024 total in 1 blocks; 912 free (0 chunks); 112 used
> CachedPlan: 1024 total in 1 blocks; 200 free (0 chunks); 824 used
> CachedPlanSource: 1024 total in 1 blocks; 96 free (0 chunks); 928 used
> SPI Plan: 1024 total in 1 blocks; 928 free (0 chunks); 96 used
> CachedPlan: 1024 total in 1 blocks; 640 free (0 chunks); 384 used
> Just one question: do you think is it possible to disable that logging sentence?
The logging printout is not your problem; or at least, it's entirely
unhelpful to regard it that way. Your problem is the out-of-memory
situation it's reporting on. As I said before, you need to investigate
what behavior of your application is causing that and take steps to
mitigate it.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-12-02 15:20:31 | Re: ARRAY_LENGTH() function behavior with empty array |
| Previous Message | Adrian Klaver | 2016-12-02 14:25:50 | Re: Using UPDATE ... RETURNING in a custom SQL function, which RETURNS integer |