From: Andres Freund <andres@anarazel.de>
To: Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Stephen Frost <sfrost@snowman.net>
Cc: Bruce Momjian <bruce@momjian.us>
Cc: David E. Wheeler <david@justatheory.com>
Cc: Christophe Pettus <christophe.pettus@pgexperts.com>
Cc: pgsql-bugs@postgresql.org
Cc: pgsql-hackers@postgresql.org
Subject: Re: [BUGS] BUG #14825: enum type: unsafe use?
Date: Tue, 3 Oct 2017 18:38:56 -0700
Message-ID: <20171004013856.2xzd2nw6oufbbtms@alap3.anarazel.de> (raw)
In-Reply-To: <a19b6647-5e64-57dc-5c34-06d9f982bff0@2ndQuadrant.com>
References: <329.1506451066@sss.pgh.pa.us>
<38835cdd-!c378-8d7a-013b-fd733c78c649@2ndQuadrant.com>
<12792.1506456422@sss.pgh.pa.us>
<20170926211419.GB7167@momjian.us>
<16025.1506461535@sss.pgh.pa.us>
<20170926214548.GQ4628@tamriel.snowman.net>
<5161729c-4597-8a41-f4e2-c7d97e84d86e@2ndQuadrant.com>
<32160eb9-60df-746b-bbc0-dd232b993d6d@2ndQuadrant.com>
<10135.1506538374@sss.pgh.pa.us>
<a19b6647-5e64-57dc-5c34-06d9f982bff0@2ndQuadrant.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
On 2017-10-03 19:53:41 -0400, Andrew Dunstan wrote:
> On 09/27/2017 02:52 PM, Tom Lane wrote:
> > Andrew Dunstan <andrew.dunstan@2ndquadrant.com> writes:
> >> At this stage on reflection I agree it should be pulled :-(
> > That seems to be the consensus, so I'll go make it happen.
> >
> >> I'm not happy about the idea of marking an input function as not
> >> parallel safe, certainly not without a good deal of thought and
> >> discussion that we don't have time for this cycle.
> > I think the way forward is to do what we had as of HEAD (984c92074),
> > but add the ability to transmit the blacklist table to parallel
> > workers. Since we expect the blacklist table would be empty most of
> > the time, this should be close to no overhead in practice. I concur
> > that the idea of marking the relevant functions parallel-restricted is
> > probably not as safe a fix as I originally thought, and it's not a
> > very desirable restriction even if it did fix the problem.
> 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.
Greetings,
Andres Freund
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: andres@anarazel.de, andrew.dunstan@2ndquadrant.com, tgl@sss.pgh.pa.us, sfrost@snowman.net, bruce@momjian.us, david@justatheory.com, christophe.pettus@pgexperts.com, pgsql-hackers@postgresql.org
Subject: Re: [BUGS] BUG #14825: enum type: unsafe use?
In-Reply-To: <20171004013856.2xzd2nw6oufbbtms@alap3.anarazel.de>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox