Re: Deadlock risk while inserting directly into partition?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: David Rowley <dgrowleyml(at)gmail(dot)com>
Cc: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Deadlock risk while inserting directly into partition?
Date: 2021-06-23 22:38:51
Message-ID: 2537253.1624487931@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

David Rowley <dgrowleyml(at)gmail(dot)com> writes:
> I've recently been thinking it would be good if you were unable to
> access partitions directly by name at all.

I strongly disagree. That's essentially betting the whole farm on
our always being able to optimize parent-level operations fully,
which I do not think we are anywhere close to.

> That would also get around
> the problem of having to lock all non-pruned partitions during queries
> to the partitioned table. Maybe it's too late for that though.

Yeah, I think we are locked into the current design now, for better
or worse.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2021-06-24 00:07:04 Re: Deadlock risk while inserting directly into partition?
Previous Message David Rowley 2021-06-23 22:27:06 Re: Deadlock risk while inserting directly into partition?