Re: Parallel worker error

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, 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:33:56
Message-ID: 3728.1504128836@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> writes:
> 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.

> 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.

My feeling is that it's going to be unreasonably expensive. Are we
going to take a lock every time we call a SECURITY DEFINER function?

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2017-08-30 22:01:23 Re: The case for removing replacement selection sort
Previous Message Regina Obe 2017-08-30 21:33:37 pg_upgrade changes can it use CREATE EXTENSION?