| From: | RekGRpth <rekgrpth(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #16974: memory leak |
| Date: | 2021-04-23 06:42:05 |
| Message-ID: | CAPgh2m+jUabhAMbzSBpL+hxydzjVM1ebEQbnnitP7PPf+E1Akw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Ok, thanks.
I solved it by reconnect on some requests and/or after some timeout
ср, 21 апр. 2021 г. в 18:27, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
>
> RekGRpth <rekgrpth(at)gmail(dot)com> writes:
> > The backend's "SHR" memory size increase from ~20Mb on startup to
> > ~150Mb by one day (with inserts and updates into table)
>
> As I said, that proves little and indeed is expected ... especially
> if your shared_buffers setting is around that. There's no leak
> unless you see VIRT increasing significantly.
>
> regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2021-04-23 10:10:39 | BUG #16980: invalid memory alloc request size |
| Previous Message | PG Bug reporting form | 2021-04-23 03:54:58 | BUG #16979: WITH RECURSIVE SQL crashes v13.x |