Vadim B. Mikheev wrote:
> Thomas G. Lockhart wrote:
> > > DATA(insert OID = 793 ( "<" PGUID 0 b t f 602 602 701 ... path_n_lt ...
> > > ^^^
> > > this is float8 but path_n_lt() returns bool...
> > >
> > > The same for all path_n_* funcs (may be others too)...
> > I'll fix this...
> Nice. There are other invalids:
> vac=> select oprname, oprcode from pg_operator where oprcanhash and oprname <> '=';
> ~= |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...
In response to
pgsql-hackers by date
|Next:||From: Bruce Momjian||Date: 1998-02-24 04:23:41|
|Subject: initdb problem|
|Previous:||From: Vadim B. Mikheev||Date: 1998-02-24 04:01:59|
|Subject: Re: [HACKERS] Re: [COMMITTERS] 'pgsql/src/bin/initdb initdb.sh'|