ports/187286: [bsd.default-versions.mk] [patch] Default PostgreSQL version needs to be updated to 9.3

[Gezeala M. Bacuño II]

Last post at pgsql-hackers list ( 'shared_memory_type' GUC as a fix?):
http://www.postgresql.org/message-id/535710DA.2050004@catalyst.net.nz

Also, below is a post that indicates that there could be performance drops
seen on Linux too although not as pronounced compared to FreeBSD:
http://www.postgresql.org/message-id/20140422.093458.864560727035836326.t-ishii@sraoss.co.jp


--

regards

gezeala bacuño II


On Mon, May 19, 2014 at 11:56 AM, Matthew Seaman <matthew at freebsd.org>wrote:

> On 19/05/2014 19:40, Dan Langille wrote:
> > Subject: Re: ports/187286: [bsd.default-versions.mk] [patch] Default
> PostgreSQL version needs to be updated to 9.3
> > Date: Mon, 19 May 2014 14:37:33 -0400
>
> >
> >  What needs to be done and how can I help?
> >
> >  Now that BSDCan is over, PGCon is about the start.  I have *all* the =
> >  PostgreSQL developers here in Ottawa.
>
> I would advise against making Pg 9.3 the default right now.  The
> performance problem exposed by Pg's switch from SysV SHM to mmap are
> quite significant, and the effect gets worse as things like eg. the size
> of work mem are increased -- so big Pg installations will get hit harder
> than small ones.
>
> There is definitely a problem from the FreeBSD side, which I believe
> Attilio is working on.  But any fixes he comes up with are going to take
> some time to percolate into general release.  It's not clear to me if
> the Pg code is doing anything "wrong" or not -- that would be good to
> establish.  Also, if there is any sort of work-around that could be
> applied to the FreeBSD port of Pg 9.3 (and presumably 9.4 et seq.) to
> mitigate the problem.
>
>         Cheers,
>
>         Matthew
>
> --
> Dr Matthew J Seaman MA, D.Phil.
> PGP: http://www.infracaninophile.co.uk/pgpkey
>
>
>