| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Pavel Luzanov <p(dot)luzanov(at)postgrespro(dot)ru> |
| Cc: | pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: ATTACH/DETACH partitions and locking |
| Date: | 2020-05-20 18:43:05 |
| Message-ID: | 20200520184305.GA20830@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On 2019-Jun-14, Pavel Luzanov wrote:
> Does it make sense to change this way?
> "Some operations require a stronger lock when using declarative partitioning
> than when using table inheritance. For example, removing a
> partition from a partitioned table requires taking an ACCESS EXCLUSIVE
> lock on the parent table, whereas a SHARE UPDATE EXCLUSIVE lock is enough in
> the case of regular inheritance."
It took long -- pushed now.
Thanks for reporting
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-05-20 19:53:23 | Re: descriptions of pg_stat_user_functions and pg_stat_slru |
| Previous Message | Fujii Masao | 2020-05-20 18:26:27 | Re: descriptions of pg_stat_user_functions and pg_stat_slru |