| From: | David Rowley <david(dot)rowley(at)2ndquadrant(dot)com> |
|---|---|
| To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Delay locking partitions during query execution |
| Date: | 2019-01-12 10:42:38 |
| Message-ID: | CAKJS1f8Q0FvNhSy8+=+ruSXoe_t8_8XP6e_YMCsaJL_81EGaUQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 4 Dec 2018 at 00:42, David Rowley <david(dot)rowley(at)2ndquadrant(dot)com> wrote:
> Over here and along similar lines to the above, but this time I'd like
> to take this even further and change things so we don't lock *any*
> partitions during AcquireExecutorLocks() and instead just lock them
> when we first access them with ExecGetRangeTableRelation().
I've attached a rebase version of this. The previous version
conflicted with some changes made in b60c397599.
--
David Rowley http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| Attachment | Content-Type | Size |
|---|---|---|
| v2-0001-Allow-lock-acquisitions-for-partitions-to-be-dela.patch | application/octet-stream | 13.1 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2019-01-12 11:32:29 | Re: Logical decoding for operations on zheap tables |
| Previous Message | David Rowley | 2019-01-12 08:49:39 | Re: speeding up planning with partitions |