From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
Cc: | "REIX, Tony" <tony(dot)reix(at)atos(dot)net>, Andres Freund <andres(at)anarazel(dot)de>, Robert Haas <robertmhaas(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, "EMPEREUR-MOT, SYLVIE" <sylvie(dot)empereur-mot(at)atos(dot)net> |
Subject: | Re: Shared Memory: How to use SYSV rather than MMAP ? |
Date: | 2018-12-26 16:43:36 |
Message-ID: | 29496.1545842616@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> writes:
> Since it's not fixing a bug, we wouldn't back-patch that into existing
> releases. But I agree that we should do something like this for
> PostgreSQL 12, and I think we should make it user configurable.
I'm -1 on making this user configurable via a GUC; that adds documentation
and compatibility burdens that we don't need, for something of no value
to 99.99% of users. The fact that the default would need to be
platform-dependent just makes that tradeoff even worse. I think the other
0.01% who need to change the default (and are bright enough to be doing
the right thing for the right reasons) could certainly handle something
like a pg_config_manual.h control symbol --- see USE_PPC_LWARX_MUTEX_HINT
for a precedent that I think applies well here. So I'd favor just doing
it that way.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2018-12-26 16:50:18 | Re: reducing the footprint of ScanKeyword (was Re: Large writable variables) |
Previous Message | David Fetter | 2018-12-26 16:38:41 | Re: reducing the footprint of ScanKeyword (was Re: Large writable variables) |