Martin Pitt <[EMAIL PROTECTED]> writes:
> I just thought about how to provide a transition path if the long-term
> solution really was to get rid of integer time stamps.
I don't think anyone has suggested doing that. In fact, there's a camp
that wishes they'd become the default. I don't see that
Hi Tom!
Tom Lane [2005-06-11 13:13 -0400]:
> Martin Pitt <[EMAIL PROTECTED]> 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?
>
Martin Pitt <[EMAIL PROTECTED]> 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.
Hi!
Andrew - Supernews [2005-06-10 23:29 -]:
> On 2005-06-10, Martin Pitt <[EMAIL PROTECTED]> wrote:
> >> As per conversation in #postgresql in freenode, it has been found that
> >> this seems to manifest on pgsql compiled using integer-datetime;
> >> float-datetime version does not have this
On 2005-06-10, Martin Pitt <[EMAIL PROTECTED]> wrote:
>> As per conversation in #postgresql in freenode, it has been found that
>> this seems to manifest on pgsql compiled using integer-datetime;
>> float-datetime version does not have this problem.
>
> I just tried to do the proposed change, howev
Hi Guillaume, hi PostgreSQL developers!
Guillaume, thanks for the great research you did!
PostgreSQL developers, the details of this are at [1], but I quote the
important bits here.
Guillaume Beaudoin [2005-06-01 11:57 -0400]:
>
> Package: postgresql
> Version: 7.4.7-6sarge1
>
> When changing
