Re: BUG #18271: Re: Postgres policy exists bug

From: Wladimir <vost_800(at)gmx(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18271: Re: Postgres policy exists bug
Date: 2024-01-05 15:52:53
Message-ID: trinity-217d610b-fe14-4b00-bde8-c7d877b25055-1704469973661@3c-app-gmx-bs41
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>I haven&#39;t thoughed about the resolving of &quot;user_id&quot; to the closed nested source</div>

<div>because I haven&#39;t discovered this side effect when I was not working with boolish filters.</div>

<div>&nbsp;</div>

<div>After considering your advice I tried to use the first example with EXISTS by replacing &quot;user_id&quot; to</div>

<div>&quot;public.inventories.user_id&quot; and the side effect wasn&#39;t there anymore. Could have know that if had made more researcher beforehand.</div>

<div>&nbsp;</div>

<div>Next time, if I find something, I will create a self-contained test case so that everyone can reproduces the error.</div>

<div>&nbsp;</div>

<div>With best regards,</div>

<div>&nbsp;</div>

<div>Wladimir</div></div></body></html>

Attachment Content-Type Size
unknown_filename text/html 850 bytes

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Vojtěch Beneš 2024-01-05 17:39:32 Re: BUG #18264: Table has type text, but query expects integer.attribute 1 of type record has wrong type
Previous Message Tom Lane 2024-01-05 15:14:17 Re: BUG #18271: Re: Postgres policy exists bug