From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | KaiGai Kohei <kaigai(at)kaigai(dot)gr(dot)jp> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, KaiGai Kohei <kaigai(at)ak(dot)jp(dot)nec(dot)com>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, HeikkiLinnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Itagaki Takahiro <itagaki(dot)takahiro(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: leaky views, yet again |
Date: | 2010-10-19 14:41:08 |
Message-ID: | 10227.1287499268@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
KaiGai Kohei <kaigai(at)kaigai(dot)gr(dot)jp> writes:
> (2010/10/19 21:31), Robert Haas wrote:
>> I think you're still misreading it.
> Hmm. In my understanding, it seems to me he concerned about possible leaky
> estimate functions, so he mentioned the horrible performance degrading, if
> we don't allow to execute these functions.
No, it wasn't about estimator functions at all, it was about what we do
in the absence of an estimator.
> So, I suggested an idea that enforces all estimate functions being installed
> by superusers; it enables us to assume they are enough safe.
Even if we were willing to accept a limitation as stringent as that,
preventing people from installing estimators is hardly going to cure
the problem.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2010-10-19 14:44:44 | Re: patch: Add JSON datatype to PostgreSQL (GSoC, WIP) |
Previous Message | Tom Lane | 2010-10-19 14:31:32 | Re: Extensions, this time with a patch |