Re: [HACKERS] BUG #14825: enum type: unsafe use?

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Stephen Frost <sfrost(at)snowman(dot)net>, Bruce Momjian <bruce(at)momjian(dot)us>, "David E(dot) Wheeler" <david(at)justatheory(dot)com>, Christophe Pettus <christophe(dot)pettus(at)pgexperts(dot)com>, Postgres-Bugs <pgsql-bugs(at)postgresql(dot)org>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [HACKERS] BUG #14825: enum type: unsafe use?
Date: 2017-10-05 13:45:14
Message-ID: CA+TgmobNQeCTY2v+tLzO54y8BLUrp+ECaKaUxs+Mp2Hb-BKCxA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

On Tue, Oct 3, 2017 at 9:38 PM, Andres Freund <andres(at)anarazel(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2017-10-05 15:38:40 Re: pg_logical_slot_peek_changes crashes postgres when called from inside pl/pgsql
Previous Message Michael Paquier 2017-10-05 05:45:53 Re: pg_logical_slot_peek_changes crashes postgres when called from inside pl/pgsql

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2017-10-05 13:47:15 Re: Postgresql gives error that role goes not exists while it exists
Previous Message Robert Haas 2017-10-05 13:44:26 Re: postgres_fdw super user checks