From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Sean Chittenden <sean(at)chittenden(dot)org>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [PATCH] PostgreSQL 9.4 mmap(2) performance regression on FreeBSD... |
Date: | 2015-03-22 02:06:39 |
Message-ID: | 20150322020639.GF10795@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Mar 19, 2015 at 12:16:07PM -0400, Bruce Momjian wrote:
> On Mon, Oct 13, 2014 at 11:35:18AM -0400, Bruce Momjian wrote:
> > On Mon, Oct 13, 2014 at 05:21:32PM +0200, Andres Freund wrote:
> > > > If we have it, we should improve it, or remove it. We might want to use
> > > > this code for something else in the future, so it should be improved
> > > > where feasible.
> > >
> > > Meh. We don't put in effort into code that doesn't matter just because
> > > it might get used elsewhere some day. By that argument we'd need to
> > > performance optimize a lot of code. And actually, using that code
> > > somewhere else is more of a counter indication than a pro
> > > argument. MAP_NOSYNC isn't a general purpose flag.
> >
> > The key is that this is platform-specific behavior, so if we should use
> > a flag to use it right, we should. You are right that optimizing
> > rarely used code with generic calls isn't a good use of time.
>
> I have adjusted Sean's mmap() options patch to match our C layout and
> plan to apply this to head, as it is from August.
Patch applied.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has their own god. +
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2015-03-22 02:15:07 | Re: No toast table for pg_shseclabel but for pg_seclabel |
Previous Message | Alvaro Herrera | 2015-03-22 01:55:52 | Re: PATCH: numeric timestamp in log_line_prefix |