From: | amul sul <sulamul(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com>, David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com> |
Subject: | Re: Partitioning with temp tables is broken |
Date: | 2018-06-13 16:55:23 |
Message-ID: | CAAJ_b94k8JapK2JyfXqgN5SgyW07exYOX1ev7iDmOoMhV8aarw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Jun 13, 2018, 8:34 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com> writes:
> > [ lots o' problems with $subject ]
>
> > But a larger question is what use such temporary partitions are?
> > Should we just prohibit adding temporary partitions to a permanant
> > partitioned table? We should allow adding temporary partitions to a
> > temporary partitioned table if only they both belong to the same
> > session.
>
> Even if you want to argue that there's a use case for these situations,
> it seems far too late in the release cycle to be trying to fix all these
> issues. I think we need to forbid the problematic cases for now, and
> leave relaxing the prohibition to be treated as a future new feature.
>
+1, forbid the problematic case.
Regards,
Amul
----------------------------------------------------------------------------------------------------
Sent from a mobile device. Please excuse brevity and tpyos.
>
From | Date | Subject | |
---|---|---|---|
Next Message | Teodor Sigaev | 2018-06-13 16:56:00 | Re: POC: GROUP BY optimization |
Previous Message | Teodor Sigaev | 2018-06-13 16:41:20 | Re: POC: GROUP BY optimization |