Re: [0/4] Proposal of SE-PostgreSQL patches - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [0/4] Proposal of SE-PostgreSQL patches
Date
Msg-id 19774.1210603957@sss.pgh.pa.us
Whole thread Raw
In response to Re: [0/4] Proposal of SE-PostgreSQL patches  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
Andrew Dunstan <andrew@dunslane.net> writes:
> Tom Lane wrote:
>> Hmm.  Is that really a good idea, compared to hard-wiring the checks
>> into nodeSeqscan and friends?

> My eyebrows went up when I read this too. Presumably, if it's hardwired 
> like you suggest then the planner can't take any account of the filter, 
> though. Do we want it to?

Well, the planner could have hardwired knowledge about the existence of
the hardwired filters --- if anything, that'd probably be easier than
hacking it to have a similar level of knowledge about generic-looking
function calls.  But in reality, since we don't know at plan time which
userid will execute the constructed plan, I'm not sure we could come up
with useful estimates anyway.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: constraint exclusion analysis caching
Next
From: Magnus Hagander
Date:
Subject: Re: [COMMITTERS] pgsql: Convert wal_sync_method to guc enum.