| From: | David Rowley <dgrowleyml(at)gmail(dot)com> |
|---|---|
| To: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
| Cc: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Deadlock risk while inserting directly into partition? |
| Date: | 2021-06-28 11:46:30 |
| Message-ID: | CAApHDvrMO7+rqQ3P0T300PtVfsvb1PwTS4z0-shvU2i-nzGvJg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, 26 Jun 2021 at 16:41, Justin Pryzby <pryzby(at)telsasoft(dot)com> wrote:
>
> On Thu, Jun 24, 2021 at 10:27:06AM +1200, David Rowley wrote:
> > I think the reasons for doing operations directly on partitions are
> > being reduced with each release. What operations do people really
> > need to do on partitions now? TRUNCATE is probably one, maybe there's
> > still a need to CREATE INDEX.
>
> We always SELECT out of parent tables, but need to be able to CREATE INDEX on
> partitions.
I imagined we'd have something along the lines of: ALTER TABLE
partitioned_table ALTER PARTITION part CREATE INDEX. I admit I don't
know how that would look when faced with multi-level partitioning.
> And INSERT ON CONFLICT into partitions,
I didn't think of that one. Looks like we're further away from
partitioning being transparent to queries and DML than I thought :-(
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Gustafsson | 2021-06-28 11:57:24 | Re: Remove redundant initializations |
| Previous Message | David Rowley | 2021-06-28 11:40:02 | Re: Remove redundant initializations |