Skip site navigation (1) Skip section navigation (2)

Re: Posix Shared Mem patch

From: Andres Freund <andres(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org, Robert Haas <robertmhaas(at)gmail(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>
Subject: Re: Posix Shared Mem patch
Date: 2012-07-03 15:55:30
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On Tuesday, July 03, 2012 05:41:09 PM Tom Lane wrote:
> Andres Freund <andres(at)2ndquadrant(dot)com> writes:
> > Btw, RhodiumToad/Andrew Gierth on irc talked about a reason why sysv
> > shared memory might be advantageous on some platforms. E.g. on freebsd
> > there is the kern.ipc.shm_use_phys setting which prevents paging out
> > shared memory and also seems to make tlb translation cheaper. There does
> > not seem to exist an alternative for anonymous mmap.
> Isn't that mlock()?
Similar at least yes. I think it might also make the virtual/physical 
translation more direct but that ist just the impression of a very short 

> > So maybe we should make that a config option?
> I'd really rather not.  If we're going to go in this direction, we
> should just go there.
I don't really care, just wanted to bring up that at least one experienced 
user would be disappointed ;). As the old implementation needs to stay around 
for EXEC_BACKEND anyway, the price doesn't seem to be too high.

Andres Freund
PostgreSQL Development, 24x7 Support, Training & Services

In response to


pgsql-hackers by date

Next:From: Tom LaneDate: 2012-07-03 15:58:01
Subject: Re: Incorrect behaviour when using a GiST index on points
Previous:From: Dimitri FontaineDate: 2012-07-03 15:52:00
Subject: Re: Event Triggers reduced, v1

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group