Re: Parallel worker error

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Parallel worker error
Date: 2017-08-30 21:28:40
Message-ID: 20170830212840.irapf5bvh7pbqp4r@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas wrote:

> In this case,
> I'll blame the fact that we allow a role to be dropped while there are
> users connected using that role. That's about as sensible as allowing
> a table to be dropped while there are users reading from it, or a
> database to be dropped while there are users connected to it, both of
> which we in fact prohibit. IOW, I'd say the problem is that we've
> allowed the system state to become inconsistent and now we're sad
> because stuff doesn't work.
>
> But since that's an established design fl^H^Hprinciple,

Actually, my first comment when Pavan mentioned this on IM was that we
should look into fixing that problem sometime. It's not terribly urgent
since it doesn't seem to hurt anything too badly, but it's still a bug.

--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Regina Obe 2017-08-30 21:33:37 pg_upgrade changes can it use CREATE EXTENSION?
Previous Message Peter Geoghegan 2017-08-30 20:23:20 Re: Polyphase merge is obsolete