Re: One process per session lack of sharing

From: AMatveev(at)bitec(dot)ru
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: One process per session lack of sharing
Date: 2016-07-14 08:41:07
Message-ID: 1572266830.20160714114107@bitec.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi

> On Tue, Jul 12, 2016 at 9:18 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> AMatveev(at)bitec(dot)ru writes:
>>> Is there any plan to implement "session per thread" or "shared
>>> sessions between thread"?
>>...
>> so
>> there's not that much motivation to do a ton of work inside the database
>> to solve it there.

> I agree that there's not really a plan to implement this, but I don't
> ...

> So, I actually think it would be a good idea to think about this.

I just want to note that converting global variables to thread-specific variables.
It's large work offcourse.
But it's not seemed to be a ton of work.
And it's the most part of refactoring for "session per thread".
Offcourse that's not all.
But it seemed to be the most valuable reason not to do that work.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2016-07-14 08:41:27 Re: Issue in pg_catalog.pg_indexes view definition
Previous Message Dilip Kumar 2016-07-14 08:29:37 Re: Issue in pg_catalog.pg_indexes view definition