| From: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Large writable variables |
| Date: | 2018-10-15 21:16:34 |
| Message-ID: | CAEepm=1_OgTWJwx6-kww7jDG=UUwMY4enWE-6VbBnQaWGNTs0Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Oct 16, 2018 at 9:07 AM Andres Freund <andres(at)anarazel(dot)de> wrote:
> $ nm -t d --size-sort -r -S src/backend/postgres|grep '\b[bB]\b'|head
> 0000000008251872 0000000000131144 b LagTracker
...
> So we have a two variables sized 130kb. Yikes.
...
> that's not actually used very often, nor in all processes... Thomas?
Yeah, here's a patch to move it in to the heap.
--
Thomas Munro
http://www.enterprisedb.com
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-Move-the-replication-lag-tracker-into-heap-memory.patch | application/octet-stream | 6.0 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-10-15 21:19:03 | Re: Large writable variables |
| Previous Message | Andres Freund | 2018-10-15 21:02:59 | Re: Large writable variables |