Re: One process per session lack of sharing

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: AMatveev(at)bitec(dot)ru
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: One process per session lack of sharing
Date: 2016-07-12 14:18:54
Message-ID: 20335.1468333134@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

AMatveev(at)bitec(dot)ru writes:
> Is there any plan to implement "session per thread" or "shared
> sessions between thread"?

No, not really. The amount of overhead that would add --- eg, the need
for locking on what used to be single-use caches --- makes the benefit
highly questionable. Also, most people who need this find that sticking
a connection pooler in front of the database solves their problem, so
there's not that much motivation to do a ton of work inside the database
to solve it there.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message AMatveev 2016-07-12 14:39:11 Re: One process per session lack of sharing
Previous Message AMatveev 2016-07-12 13:57:57 One process per session lack of sharing