On 11/29/20 3:44 PM, James Coleman wrote:
> On Mon, Nov 23, 2020 at 8:19 AM James Coleman <jtc331@gmail.com> wrote:
>>
>> ..
>>
>> So I'm +1 on turning it into an ERROR log instead, since it seems to
>> me that encountering this case would almost certainly represent a bug
>> in path generation.
>
> Here's a patch to do that.
>
Thanks. Isn't the comment incomplete? Should it mention just parallel
safety or also volatility?
regards
--
Tomas Vondra
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company