Re: range test for hash index?
Amit Kapila <amit.kapila16@gmail.com>
From: Amit Kapila <amit.kapila16@gmail.com>
To: Tomas Vondra <tomas.vondra@2ndquadrant.com>
Cc: Paul A Jungwirth <pj@illuminatedcomputing.com>,
Jeff Davis <pgsql@j-davis.com>, Heikki Linnakangas <heikki.linnakangas@iki.fi>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2019-09-27T04:18:07Z
Lists: pgsql-hackers
On Fri, Sep 27, 2019 at 6:02 AM Amit Kapila <amit.kapila16@gmail.com> wrote: > > On Fri, Sep 27, 2019 at 4:03 AM Tomas Vondra > <tomas.vondra@2ndquadrant.com> wrote: > > > > > > By "inconsistent" you mean that pre-10 versions will have different > > expected output than versions with WAL-logged hash indexes? > > > > Yes. > > > I don't see > > why that would be a reason not to backpatch to all supported versions, > > considering we already have the same difference for other test suites. > > > > Yeah, I also think so. I will do this today. > Pushed. -- With Regards, Amit Kapila. EnterpriseDB: http://www.enterprisedb.com
Commits
-
Fix oversight in commit 4429f6a9e3e12bb4af6e3677fbc78cd80f160252.
- 668918ff1378 9.4.25 landed
- 8364ef925c59 9.5.20 landed
- 89c98c6ce36a 9.6.16 landed
- d395b1e901c0 10.11 landed
- 84ced048d18d 11.6 landed
- fb341a7db9ba 12.0 landed
- bb0e3ce8eb07 13.0 landed
-
Support range data types.
- 4429f6a9e3e1 9.2.0 cited