Re: dynamic shared memory: wherein I am punished for good intentions

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Peter Geoghegan <pg(at)heroku(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: dynamic shared memory: wherein I am punished for good intentions
Date: 2013-10-10 18:45:18
Message-ID: CA+TgmoZkdrUBN5FgyOuED0oxDbCGmyqc02=PmdQPcOmF6DrveA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Oct 10, 2013 at 2:36 PM, Peter Geoghegan <pg(at)heroku(dot)com> wrote:
> On Thu, Oct 10, 2013 at 9:13 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>> (2) Default to using System V shared memory. If people want POSIX
>> shared memory, let them change the default.
>
>> After some consideration, I think my vote is for option #2.
>
> Wouldn't that become the call of packagers?

Packagers can certainly override whatever we do, but we still need to
make the buildfarm green again.

> Wasn't there already some
> reason why it was advantageous for FreeBSD to continue to use System V
> shared memory?

Yes, but this code doesn't affect the main shared memory segment, so I
think that's sort of a separate point.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Josh Berkus 2013-10-10 18:45:21 Re: Auto-tuning work_mem and maintenance_work_mem
Previous Message Peter Geoghegan 2013-10-10 18:44:51 Re: Auto-tuning work_mem and maintenance_work_mem