----------------------------------------------------------------
Moray.McConnachie@computing-services.oxford.ac.uk
----- Original Message -----
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alex Howansky <alex@wankwood.com>
Cc: <pgsql-sql@postgreSQL.org>
Sent: Thursday, February 24, 2000 11:57 PM
Subject: Re: [SQL] how to create index on timestamp field in pre v7
database
> Alex Howansky <alex@wankwood.com> writes:
> > My question is, how "equivalent" are these types?
>
> They're the same code: we jacked up the name "timestamp" and rolled
the
> old datetime code underneath. Strictly a matter of coming closer to
> the SQL standard names for these datatypes.
>
> > Can I use datetime_ops to index a timestamp field in a v6.5.3
database?
>
> Similarly, "datetime_ops" in 6.5 is now "timestamp_ops".
>
> As a rule, I'd suggest not bothering with opclasses in index
> declarations. The only situation where you need to select one is
> where there is more than one possible opclass for the same datatype.
> This holds for some of the geometric types, but not for any plain
scalar
> types like numerics or date/time types. (You could think of an
opclass
> as specifying which sort order the index uses...)
Agreed - but note that pg_dump currently produces CREATE INDEX
statements with opclasses included.
That means running a script created by pg_dump v.6.5.x will fail under
7.0 because there is no index opclass of the type datetime?
Judging from my brief experiments that looks to be the case, anyway.
It looks like replacing all occurrences of datetime with timestamp in
the script works - even for the few functions I have that used the
datetime() function.
Yours,
Moray
