On Sat, 19 Jan 2019 at 12:05, John Naylor <jcnay...@gmail.com> wrote: > > On 11/22/18, David Rowley <david.row...@2ndquadrant.com> wrote: > > If required, such operations could LOCK TABLE the top partitioned > > table to block the DML operation. There's already a risk of similar > > deadlocks from such operations done on multiple separate tables when > > the order they're done is not the same as the order the tables are > > written in a query, although, in that case, the window for the > > deadlock is likely to be much smaller. > > Is this something that would need documentation anywhere?
Probably at least the release notes. I'm unsure where else to mention it. I don't feel the workaround of using LOCK TABLE is special to this case. The patch does, however, make it a possible requirement for performing DDL on individual partitions where it was not previously. -- David Rowley http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services
