| 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-24 09:08:48 |
| Message-ID: | CA+HiwqEStonNz+1eHy68MfHQMmEmdX79TYR0=A2t=pG4D9LUdQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Dec 23, 2019 at 6:42 PM Amit Langote <amitlangote09(at)gmail(dot)com> wrote:
> 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 didn't look into that either. I wouldn't propose back-patching that,
> > but it'd be interesting to try to fix it in HEAD.
>
> Agreed.
I gave that a try and ended up with attached that applies on top of
your delay-loading-relcache-partition-data-2.patch.
Thanks,
Amit
| Attachment | Content-Type | Size |
|---|---|---|
| wholerow-partition-key.patch | text/plain | 12.2 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fabien COELHO | 2019-12-24 10:17:31 | pgbench - use pg logging capabilities |
| Previous Message | Amit Khandekar | 2019-12-24 09:01:02 | Re: logical decoding : exceeded maxAllocatedDescs for .spill files |