On Wed, Dec 21, 2016 at 4:24 PM, Craig Ringer <cr...@2ndquadrant.com> wrote: >> Is anyone working on fixing this for PostgreSQL 10? > > Not as far as I know. > > IMO this and other similar cases should all be handled the same way: > create the constraint NOT VALID, then VALIDATE it while holding a weak > lock that only blocks concurrent schema changes.
Sounds like a good approach. Similar to what we (Trustly) did when we sponsored the FOR KEY LOCK feature to improve concurrency, we would be very interested in also sponsoring this feature, as it would mean a great lot to us. I don't know if this is the right forum trying to find someone/some company to sign up for the task, please let me know if I should mail to some other list. Thanks. Joel Jacobson Trustly -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
