Re: BUG #15534: Operators from public schema in trigger WHEN-clauses are silently allowed despite breaking restores

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org, p(dot)otoole(at)uwyo(dot)edu
Subject: Re: BUG #15534: Operators from public schema in trigger WHEN-clauses are silently allowed despite breaking restores
Date: 2018-12-01 16:42:59
Message-ID: 18136.1543682579@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> writes:
> What's happening here is that IS DISTINCT FROM has a hidden search_path
> search in it, that ruleutils doesn't (and can't) handle.

Right. A few months ago I posted a list of problems of this ilk
(IS DISTINCT FROM is far from the only trouble spot). Too lazy to
search the archives for it right now, but the discussion kinda went
nowhere AFAIR.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Ananth Thomas 2018-12-03 05:21:27 Postgres Sequence issue
Previous Message Andrew Gierth 2018-12-01 14:40:08 Re: BUG #15534: Operators from public schema in trigger WHEN-clauses are silently allowed despite breaking restores