Re: Large writable variables

From: Andres Freund <andres(at)anarazel(dot)de>
To: Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Large writable variables
Date: 2018-10-15 21:57:56
Message-ID: 20181015215756.pdhi2hqxofphvcxe@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2018-10-16 10:16:34 +1300, Thomas Munro wrote:
> 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

> From f3fb64e67c1e86e11dfafc8a712e9750f650f60b Mon Sep 17 00:00:00 2001
> From: Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>
> Date: Tue, 16 Oct 2018 10:08:57 +1300
> Subject: [PATCH] Move the replication lag tracker into heap memory.
>
> Andres Freund complained about the 128KB of .bss occupied by LagTracker.
> It's only needed in the walsender process, so allocate it in heap
> memory there.

Cool, let's do that.

Greetings,

Andres Freund

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2018-10-15 22:11:15 Re: Large writable variables
Previous Message Jonathan S. Katz 2018-10-15 21:34:14 Re: PostgreSQL 11 RC1 + GA Dates