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

From: Peter Geoghegan <pg(at)heroku(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Daniel Newman <dtnewman(at)gmail(dot)com>, danielnewman(at)umich(dot)edu, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #14210: filter by "=" constraint doesn't work when hash index is present on a column
Date: 2016-07-11 18:27:34
Message-ID: CAM3SWZTwjYk8NpKs0r6cP__gQtBrVOy36Z+ShrrOBc-JDLdkBw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Mon, Jun 27, 2016 at 1:31 PM, Peter Geoghegan <pg(at)heroku(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message bossartn 2016-07-11 22:36:41 BUG #14242: Role with a setconfig "role" setting to a nonexistent role causes pg_upgrade to fail
Previous Message Tom Lane 2016-07-11 17:08:40 Re: BUG #14237: Terrible performance after accidentally running 'drop index' for index still being created