On Sat, 2012-09-08 at 16:35 -0400, Tom Lane wrote: > and obviously, python is iterating through the hash's keys in a > different order than it was a minor version or two back. (The failure > is occurring with 3.3.0-0.4.rc1.fc19, whereas I saw no failure with > 3.2.3-7.fc17.)
Yes, known problem with 3.3. > > I think probably the best thing is to change the test case so it has > one > valid key and one not-valid one, rather than assuming that the same > key > will always be complained of when there's more than one not-valid > one. That would probably work. We dealt with a similar problem in 2cfb1c6f77734db81b6e74bcae630f93b94f69be, if you want some additional inspiration. Not sure why we didn't see this case then. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
