From: | "Thomas G(dot) Lockhart" <lockhart(at)alumni(dot)caltech(dot)edu> |
---|---|
To: | "Vadim B(dot) Mikheev" <vadim(at)sable(dot)krasnoyarsk(dot)su> |
Cc: | hackers(at)postgresql(dot)org |
Subject: | Re: [HACKERS] regression: select_views.sql |
Date: | 1998-02-24 04:16:49 |
Message-ID: | 34F249B1.BB202B1E@alumni.caltech.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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 <> '=';
> 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...
- Tom
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 1998-02-24 04:23:41 | initdb problem |
Previous Message | Vadim B. Mikheev | 1998-02-24 04:01:59 | Re: [HACKERS] Re: [COMMITTERS] 'pgsql/src/bin/initdb initdb.sh' |