| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com> |
| Cc: | 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 15:03:59 |
| Message-ID: | 29916.1528902239@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2018-06-13 15:04:19 | Re: Index maintenance function for BRIN doesn't check RecoveryInProgress() |
| Previous Message | Alvaro Herrera | 2018-06-13 14:51:06 | Re: Index maintenance function for BRIN doesn't check RecoveryInProgress() |