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+TgmobNQeCTY2v+tLzO54y8BLUrp+ECaKaUxs+Mp2Hb-BKCxA@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] [BUGS] BUG #14825: enum type: unsafe use?  (Andres Freund <andres@anarazel.de>)
Responses Re: [HACKERS] [BUGS] BUG #14825: enum type: unsafe use?
Re: [HACKERS] [BUGS] BUG #14825: enum type: unsafe use?
List pgsql-bugs
On Tue, Oct 3, 2017 at 9:38 PM, Andres Freund <andres@anarazel.de> wrote:
>> Do you have any suggestion as to how we should transmit the blacklist to
>> parallel workers?
>
> How about storing them in the a dshash table instead of dynahash?
> Similar to how we're now dealing with the shared typmod registry stuff?
> It should be fairly simple to now simply add a new struct Session member
> shared_enum_whatevs_table.

Yeah, that approach seems worth exploring.

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


-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

pgsql-bugs by date:

Previous
From: Michael Paquier
Date:
Subject: Re: [BUGS] pg_logical_slot_peek_changes crashes postgres when calledfrom inside pl/pgsql
Next
From: Tom Lane
Date:
Subject: Re: [BUGS] pg_logical_slot_peek_changes crashes postgres when called from inside pl/pgsql