| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Jan Wieck <jan(at)wi3ck(dot)info>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Craig Ringer <craig(at)2ndquadrant(dot)com>, AMatveev(at)bitec(dot)ru, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: One process per session lack of sharing |
| Date: | 2016-07-18 19:53:09 |
| Message-ID: | 20160718195309.3rc74dwcdkobaogm@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2016-07-18 15:47:58 -0400, Robert Haas wrote:
> I think the risk profile is exactly the opposite of what you are
> suggesting here. If we provide an option to compile the server with
> all global variables converted to thread-local variables, there's
> really not a whole lot that can break, AFAICS.
Using TLS will slow down things noticeably though. So if we were to go
there, we'd have to make up for some constant slowdown.
> We'll technically be multi-threaded but the code need not know or care
> about the other threads; only in the event of a memory clobber can
> they affect each other.
But that'll make it pretty hard to take advantage of multi-threading to
a meaningful degree. Except for being able to create shared memory after
the fact - quite useful! - there'd not be much point.
- Andres
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Emre Hasegeli | 2016-07-18 20:54:13 | Re: Floating point comparison inconsistencies of the geometric types |
| Previous Message | Robert Haas | 2016-07-18 19:47:58 | Re: One process per session lack of sharing |