| From: | Amit Langote <amitlangote09(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: unsupportable composite type partition keys |
| Date: | 2019-12-26 01:41:08 |
| Message-ID: | CA+HiwqH1k4hhKvRXHTgFRKO=i6q9xj5OU3g7dHTsEf1=Z96O9A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Dec 26, 2019 at 5:45 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Amit Langote <amitlangote09(at)gmail(dot)com> writes:
> >> On Sun, Dec 22, 2019 at 6:13 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> >>> I wonder whether we couldn't also lift
> >>> the restriction against whole-row Vars in partition expressions.
> >>> Doesn't seem like there is much difference between such a Var and
> >>> a row(...)::table_rowtype expression.
>
> > I gave that a try and ended up with attached that applies on top of
> > your delay-loading-relcache-partition-data-2.patch.
>
> Pushed with minor fixes.
Thank you.
Regards,
Amit
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Korotkov | 2019-12-26 01:59:48 | Re: Avoid full GIN index scan when possible |
| Previous Message | Tatsuo Ishii | 2019-12-26 00:26:39 | Re: Implementing Incremental View Maintenance |