| From: | Amit Langote <amitlangote09(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: CVE-2017-7484-induced bugs, or, btree cmp functions are not leakproof? |
| Date: | 2018-10-22 14:03:03 |
| Message-ID: | CA+HiwqE+YMtM8RZtEGxS6yC8HFqEmZUrx4D-Gn=Xmn0gZRtCQQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Jul 14, 2018 at 11:29 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> writes:
> > ... For
> > partitioning, we can rely on all the columns being inherited, but not
> > for plain inheritance.
>
> Uh, what?
Maybe he meant that partitioning doesn't allow locally defined columns
in children, but plain inheritance does. Btw, Peter also said this
earlier in the paragraph:
"This could also happen through inheritance, so we should check that as
well, but we need to make sure that the particular column is inherited
and not added locally."
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.
Thanks,
Amit
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Fetter | 2018-10-22 14:10:32 | Re: Side effect of CVE-2017-7484 fix? |
| Previous Message | PG Bug reporting form | 2018-10-22 14:00:50 | BUG #15449: file_fdw using program cause exit code error when using LIMIT |