| 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 01:20:28 |
| Message-ID: | CA+HiwqHYfc8taAAE2O46UbDRR3VQ7FEZYyzrHDi60a4D-0Vp6w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Dec 24, 2019 at 12:00 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> BTW, I forgot to mention: while I think the patch to forbid pseudotypes
> by using CheckAttributeType() can be back-patched, I'm leaning towards
> not back-patching the other patch. The situation where we get into
> infinite recursion seems not very likely in practice, and it's not
> going to cause any crash or data loss, so I think we can just say
> "sorry that's not supported before v13". The patch as I'm proposing
> it seems rather invasive for a back-branch fix.
It is indeed.
Just to be sure, by going with "unsupported before v13", which one do you mean:
* documenting it as so
* giving an error in such cases, like the patch in the first email on
this thread did
* doing nothing really
Thanks,
Amit
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin Pryzby | 2019-12-24 01:24:28 | Re: error context for vacuum to include block number |
| Previous Message | Tom Lane | 2019-12-23 21:33:55 | Re: unsupportable composite type partition keys |