From: | "Vadim B(dot) Mikheev" <vadim(at)sable(dot)krasnoyarsk(dot)su> |
---|---|
To: | "Thomas G(dot) Lockhart" <lockhart(at)alumni(dot)caltech(dot)edu> |
Cc: | hackers(at)postgresql(dot)org |
Subject: | Re: [HACKERS] regression: select_views.sql |
Date: | 1998-02-24 04:26:09 |
Message-ID: | 34F24BE1.5D73C888@sable.krasnoyarsk.su |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Thomas G. Lockhart wrote:
>
> >
> > vac=> select oprname, oprcode from pg_operator where oprcanhash and oprname <> '=';
> > oprname|oprcode
> > -------+------------
> > ~= |intervalsame
> > ^^^^^^^^^^^^^^^^^^^^ ok, but others are not!
> > <> |intervalne
> > < |intervallt
> > > |intervalgt
> > <= |intervalle
> > >= |intervalge
> > (6 rows)
>
> Hmm. Those look like they support the "time interval" type, which I haven't been updating
> because it is based on abstime; I'm more interested in the wider-range/more-precise
> datetime-based stuff. I would think about rewriting the time interval routines, but
> assume it was used somewhere in the backend to support time travel. Don't know if it is
> still in there somewhere...
I just say that all these <>, <, >, >=, <= must have FALSE in oprcanhash.
Having TRUE for them is bug.
Vadim
From | Date | Subject | |
---|---|---|---|
Next Message | The Hermit Hacker | 1998-02-24 04:38:43 | Re: [HACKERS] Re: [COMMITTERS] 'pgsql/src/bin/initdb initdb.sh' |
Previous Message | Bruce Momjian | 1998-02-24 04:23:41 | initdb problem |