Re: [COMMITTERS] pgsql: Introduce dynamic shared memory areas.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [COMMITTERS] pgsql: Introduce dynamic shared memory areas.
Date: 2016-12-05 19:32:40
Message-ID: 25856.1480966360@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Mon, Dec 5, 2016 at 1:08 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Also, given that the idea of
>> DSA seems to be to support a number of different use-cases, I'm not
>> sure that it's useful to have a knob that limits the total consumption
>> rather than individual areas. IOW: who exactly is going to call
>> dsa_set_size_limit, and on what grounds would they compute the limit?

> The code that creates the DSA is going to call it.

Ah, I misunderstood: from the name of the field and the way you'd
described it, I thought it was a limit on the total space used across
all DSAs. A per-DSA limit does make sense.

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Robert Haas 2016-12-05 20:14:01 Re: [COMMITTERS] pgsql: Introduce dynamic shared memory areas.
Previous Message Robert Haas 2016-12-05 19:12:24 pgsql: libpq: Fix another bug in 721f7bd3cbccaf8c07cad2707826b83f846948

Browse pgsql-hackers by date

  From Date Subject
Next Message Jim Nasby 2016-12-05 19:48:03 Separate connection handling from backends
Previous Message Robert Haas 2016-12-05 19:12:26 Re: Patch: Implement failover on libpq connect level.