Andrew - Supernews <[EMAIL PROTECTED]> writes:
> Looking more closely, the significant thing seems to be that neither of my
> 7.4 servers is on 7.4.7, and this seems to have been fixed there (in response
> to bug 1331).
1332 you mean. Yeah, I was testing on 7.4.7, so this is almost
certainly a du
On 2005-04-29, Tom Lane <[EMAIL PROTECTED]> wrote:
> Andrew - Supernews <[EMAIL PROTECTED]> writes:
>> I did some analysis for this one when it was mentioned just now in the irc
>> chan. I can reproduce on 7.4.x as follows:
>
>> test=> set timezone to 'America/Buenos_Aires';
>> SET
>> test=> select
Andrew - Supernews <[EMAIL PROTECTED]> writes:
> I did some analysis for this one when it was mentioned just now in the irc
> chan. I can reproduce on 7.4.x as follows:
> test=> set timezone to 'America/Buenos_Aires';
> SET
> test=> select age(date '2005-05-05', date '1964-05-05');
>
On 2005-04-28, "J.Simon Goodall" <[EMAIL PROTECTED]> wrote:
>
> The following bug has been logged online:
>
> Bug reference: 1637
> Logged by: J.Simon Goodall
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 7.4.2
> Operating system: Linux
> Description:age() fu
"J.Simon Goodall" <[EMAIL PROTECTED]> writes:
> With the same query the age function is giving me two results, one as it
> should be (34 years) and the other one is off by 1 hour,
Daylight-savings time shift?
regards, tom lane
---(end of broadcast)
The following bug has been logged online:
Bug reference: 1637
Logged by: J.Simon Goodall
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4.2
Operating system: Linux
Description:age() function is giving different results
Details:
With the same query the age fu
