On Sun, Dec 3, 2017 at 10:30 PM, Amit Kapila <amit.kapil...@gmail.com> wrote: > I thought there are some cases (though less) where we want to Shutdown > the nodes (ExecShutdownNode) earlier and release the resources sooner. > However, if you are not completely sure about this change, then we can > leave it as it. Thanks for sharing your thoughts.
OK, thanks. I committed that patch, after first running 100 million tuples through a Gather over and over again to test for leaks. Hopefully I haven't missed anything here, but it looks like it's solid. Here once again are the remaining patches. While the already-committed patches are nice, these two are the ones that actually produced big improvements in my testing, so it would be good to move them along. Any reviews appreciated. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
0001-shm-mq-less-spinlocks-v2.patch
Description: Binary data
0002-shm-mq-reduce-receiver-latch-set-v1.patch
Description: Binary data
