RE: [HACKERS] int8 and index

From: "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp>
To: "Bruce Momjian" <maillist(at)candle(dot)pha(dot)pa(dot)us>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <t-ishii(at)sra(dot)co(dot)jp>, <pgsql-hackers(at)postgreSQL(dot)org>
Subject: RE: [HACKERS] int8 and index
Date: 1999-09-27 01:08:55
Message-ID: 001601bf0884$de79e920$2801007e@cadzone.tpf.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> -----Original Message-----
> From: Bruce Momjian [mailto:maillist(at)candle(dot)pha(dot)pa(dot)us]
> Sent: Monday, September 27, 1999 9:47 AM
> To: Tom Lane
> Cc: t-ishii(at)sra(dot)co(dot)jp; Hiroshi Inoue; pgsql-hackers(at)postgreSQL(dot)org
> Subject: Re: [HACKERS] int8 and index
>
>
> > Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> writes:
> > >> How about select .. from .. where .. = ..::int8; ?
> > >>
> > >> Without ::int8 PostgreSQL doesn't use int8 indexes.
> >
> > > Oops. I forgot about that! Thanks.
> >
> > Yes, this is on the TODO list (although I think TODO just mentions
> > the equivalent problem for int2).
> >
>
> int8 mention added.
>

There may be a little difference.

int4 -> int8 never fails.
But int4 -> int2 fails if abs(int4) > 32768.

select .. from .. where int2_column = 32769;

should return 0 rows or cause an elog(ERROR) ?

Regards.

Hiroshi Inoue
Inoue(at)tpf(dot)co(dot)jp

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 1999-09-27 03:26:05 Re: [HACKERS] A multi-lang patch for psql 6.5.1 (fwd)
Previous Message Bruce Momjian 1999-09-27 00:47:04 Re: [HACKERS] int8 and index