On 12/05/2014 08:04 AM, Simon Riggs wrote: > On 6 December 2014 at 00:45, Merlin Moncure <mmoncure@xxxxxxxxx> wrote: > >> Neat -- got any test cases (would this have prevented OP's problem)? > > No test case was posted, so I am unable to confirm. > > A test case I produced that appears to be the same issue is fixed. > > I await confirmation from the OP. > So that's proprietary/confidential data. However, the company involved has a large testbed and I could test their data using a patched version of Postgres. In 3 months their data distribution has drifted, so I'll need to do some work to recreate the original bad plan circumstances. I'll keep you posted on how the patch works for that setup. It would be great to come up with a generic/public test for a bad abort-early situation. Ideas? -- Josh Berkus PostgreSQL Experts Inc. http://pgexperts.com -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
