Re: BUG #14210: filter by "=" constraint doesn't work when hash index is present on a column - Mailing list pgsql-bugs

From Peter Geoghegan
Subject Re: BUG #14210: filter by "=" constraint doesn't work when hash index is present on a column
Date
Msg-id CAM3SWZTwjYk8NpKs0r6cP__gQtBrVOy36Z+ShrrOBc-JDLdkBw@mail.gmail.com
Whole thread Raw
In response to Re: BUG #14210: filter by "=" constraint doesn't work when hash index is present on a column  (Peter Geoghegan <pg@heroku.com>)
List pgsql-bugs
On Mon, Jun 27, 2016 at 1:31 PM, Peter Geoghegan <pg@heroku.com> wrote:
> Understood. It's on my TODO list for the week, although I'll
> prioritize isolating and fixing that UPSERT "attempted to delete
> invisible tuple" bug.

I would like to start work on this immediately, but feel it's
premature until my other tuplesort testing patch gets some review [1].

[1] https://www.postgresql.org/message-id/CAM3SWZSgxehDkDMq1FdiW2A0Dxc79wH0hz1x-TnGy=1BXEL+nw@mail.gmail.com
--
Peter Geoghegan

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #14237: Terrible performance after accidentally running 'drop index' for index still being created
Next
From: bossartn@amazon.com
Date:
Subject: BUG #14242: Role with a setconfig "role" setting to a nonexistent role causes pg_upgrade to fail