=20
> > It appears that the timestamp 'epoch' is being interpreted as
> > relative to the local timezone, rather than being an absolute time.
>=20
> This is correct for timestamp ... you want timestamp with time zone.
Sorry, but that's dumb (IMHO). The unix epoch is not relative to the
local timezone.
I'm now using a function to convert from unix times to timestamps, since
the alternative is ugly and verbose even by SQL standards...
create function epoch(integer)
returns timestamp with time zone
as 'select timestamp with time zone \'epoch\'
+ interval \'1 second\' * $1;'
language sql immutable;
Is there a better way?
Steve.
