Re: Bug#311533: Invalid timestamp returned because of timezone

Martin Pitt <martin(at)piware(dot)de> writes:
> This would require that support for both int and float timestamps is
> present in the postmaster, but wouldn't require an immediate dump and
> reload of all databases. Would that be possible in any way?

Given infinite amounts of work, anything is possible. However, I'd rate
the chances of the above actually happening as about nil. The chances
of it happening in an existing stable release branch are flat-out zero.
We don't make major feature additions in stable branches; that's why
they are stable ;-)

I'm not sure why you are asking for this anyway: it wouldn't do anything
to solve the immediate problem for existing users. What *would* do
something for them is to apply the patch already committed to our CVS.

2005-06-04 21:48 tgl

* src/backend/commands/: variable.c (REL7_3_STABLE), variable.c
(REL7_4_STABLE), variable.c (REL8_0_STABLE), variable.c: Code for
SET/SHOW TIME ZONE with a fixed-interval timezone was not prepared
for HAVE_INT64_TIMESTAMP. Per report from Guillaume Beaudoin.

regards, tom lane