2010/9/1 KaiGai Kohei <kaigai(at)ak(dot)jp(dot)nec(dot)com>:
> Right now, it stands on a strict assumption that considers operators
> implemented with built-in functions are safe; it does not have no
> possibility to leak supplied arguments anywhere.
> Please note that this patch does not case about a case when
> a function inside a view and a function outside a view are
> distributed into same level and the later function has lower
> cost value.
Without making some attempt to address these two points, I don't see
the point of this patch.
Also, I believe we decided previously do this deoptimization only in
case the user requests it with CREATE SECURITY VIEW.
The Enterprise Postgres Company
In response to
pgsql-hackers by date
|Next:||From: Robert Haas||Date: 2010-09-02 02:58:13|
|Subject: Re: multibyte charater set in levenshtein function|
|Previous:||From: Tom Lane||Date: 2010-09-02 00:57:43|
|Subject: Re: compiling with RELCACHE_FORCE_RELEASE doesn't pass regression |