Re: [HACKERS] [BUGS] BUG #14825: enum type: unsafe use? - Mailing list pgsql-bugs

From Robert Haas
Subject Re: [HACKERS] [BUGS] BUG #14825: enum type: unsafe use?
Date
Msg-id CA+TgmoaJ-8QtU4qRdd73uOEkG1pQu1hdsrd++OmkkxRBYyR6ig@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] [BUGS] BUG #14825: enum type: unsafe use?  (Thomas Munro <thomas.munro@enterprisedb.com>)
Responses Re: [HACKERS] [BUGS] BUG #14825: enum type: unsafe use?
Re: [HACKERS] [BUGS] BUG #14825: enum type: unsafe use?
List pgsql-bugs
On Thu, Jan 11, 2018 at 6:01 PM, Thomas Munro
<thomas.munro@enterprisedb.com> wrote:
> [ the data isn't session lifetime ]
>
> So I agree with Tom's suggestion:
>
> On Wed, Oct 4, 2017 at 2:29 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Perhaps serialize the contents into an array in DSM, then rebuild a hash
>> table from that in the worker.  Robert might have a better idea though.
>
> I'd happily volunteer to write or review a patch to do that.  Is there
> a rebase of the stuff that got reverted, to build on?

Those seem like reasons not to use Session, but not necessarily
reasons not to have the leader directly build the dshash that the
workers access rather than building a separate hash table in every
worker.

Maybe having every worker build a separate hash table is a good idea
for some reason, but it's not clear to me that you've stated such a
reason.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-bugs by date:

Previous
From: Andres Freund
Date:
Subject: Re: BUG #14932: SELECT DISTINCT val FROM table gets stuck in aninfinite loop
Next
From: Thomas Munro
Date:
Subject: Re: [HACKERS] [BUGS] BUG #14825: enum type: unsafe use?