From: Tom Lane <tgl@sss.pgh.pa.us>
To: Amit Langote <amitlangote09@gmail.com>
cc: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>,
        PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: CVE-2017-7484-induced bugs, or,
 btree cmp functions are not leakproof?
In-reply-to: 
 <CA+HiwqE+YMtM8RZtEGxS6yC8HFqEmZUrx4D-Gn=Xmn0gZRtCQQ@mail.gmail.com>
References: <3876.1531261875@sss.pgh.pa.us> <11560.1531349520@sss.pgh.pa.us>
 <3ad75dc5-4ae7-087a-f2f8-b3bd92a8b2b0@2ndquadrant.com>
 <1029.1531578563@sss.pgh.pa.us>
 <CA+HiwqE+YMtM8RZtEGxS6yC8HFqEmZUrx4D-Gn=Xmn0gZRtCQQ@mail.gmail.com>
Comments: In-reply-to Amit Langote <amitlangote09@gmail.com>
	message dated "Mon, 22 Oct 2018 23:03:03 +0900"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <83024.1540217851.1@sss.pgh.pa.us>
Date: Mon, 22 Oct 2018 10:17:31 -0400
Message-ID: <83025.1540217851@sss.pgh.pa.us>
Precedence: bulk

Amit Langote <amitlangote09@gmail.com> writes:
> On Sat, Jul 14, 2018 at 11:29 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Peter Eisentraut <peter.eisentraut@2ndquadrant.com> writes:
>>> ... For
>>> partitioning, we can rely on all the columns being inherited, but not
>>> for plain inheritance.

>> Uh, what?

> But maybe for the case under question, that's irrelevant, because
> we're only interested in access to inherited columns as those are the
> only ones that can be accessed in queries via parent.

Yeah, that's what I thought.  It seems like it should be possible to base
all stats access decisions off the table actually named in the query,
because only columns appearing in that table could be referenced, and only
that table's permissions actually get checked at runtime.

I guess it's possible that a child table could have, say, an index on
column X (inherited) and column Y (local) and that some aspect of costing
might then be interested in the behavior of column Y, even though the
query could only mention X not Y.  But then we could fall back to the
existing behavior.

			regards, tom lane