On Tue, 27 Feb 2007, Tom Lane wrote:
No, because for the "standard" regression behavior we have variant
result files both with and without the DST law change: see horology and
horology_1. The issue only comes up for machines that were matching to
horology-no-DST-before-1970.out (which may be
Kris Jurka <[EMAIL PROTECTED]> writes:
> Shouldn't all of the buildfarm members be failing either before or after
> the patch? That doesn't seem to be the case for any of them.
No, because for the "standard" regression behavior we have variant
result files both with and without the DST law chang
On Tue, 27 Feb 2007, Kris Jurka wrote:
I'll look at an upgrade. Eel is failing as well, but surprisingly canary is
not. Canary hasn't had any updates applied, so why isn't it failing as well:
Shouldn't all of the buildfarm members be failing either before or after
the patch? That doesn
On Tue, 27 Feb 2007, Tom Lane wrote:
I see that kudu and dragonfly are now failing regression in the 7.3 and
7.4 branches, as a consequence of this patch:
http://archives.postgresql.org/pgsql-committers/2007-02/msg00491.php
Is it reasonable to assume that that machine will soon be patched to
Tom Lane wrote:
I see that kudu and dragonfly are now failing regression in the 7.3 and
7.4 branches, as a consequence of this patch:
http://archives.postgresql.org/pgsql-committers/2007-02/msg00491.php
Is it reasonable to assume that that machine will soon be patched to
know about the new US DS
I see that kudu and dragonfly are now failing regression in the 7.3 and
7.4 branches, as a consequence of this patch:
http://archives.postgresql.org/pgsql-committers/2007-02/msg00491.php
Is it reasonable to assume that that machine will soon be patched to
know about the new US DST rules? If not,
