So it's not hardware and doesn't seem to be Windows version specific (my
tests were run on XPPro).
Looks like we have some major digging to do :-(
cheers
andrew
Petr Jelinek wrote:
I did some testing and I think that I can confirm this - on my
workstation under Windows 2000 with latest CV
I did some testing and I think that I can confirm this - on my
workstation under Windows 2000 with latest CVS and gcc 3.2.3 it randomly
fails (it sometimes works and sometimes fails even with same binary) on
prepared_xacts and always fails on rules.
Tested 3 rebuilds and about 10 checks on eac
> -Original Message-
> From: Andrew Dunstan [mailto:[EMAIL PROTECTED]
> Sent: 14 July 2005 15:17
> To: Dave Page
> Cc: Tom Lane; PostgreSQL-development
> Subject: Re: [HACKERS] windows regression failure - prepared xacts
>
>
> >Yep, no problem there. Wel
Dave Page wrote:
Short answer:
. your box will need to be able to contact http://www.pgbuildfarm.org
either directly or via proxy, and it wiull need access to a CVS repo,
either the one at postgresql.org or a mirror (you can set up your own
mirror using CSVup on a linux or FBSD box).
> -Original Message-
> From: Andrew Dunstan [mailto:[EMAIL PROTECTED]
> Sent: 14 July 2005 14:36
> To: Dave Page
> Cc: Tom Lane; PostgreSQL-development
> Subject: Re: [HACKERS] windows regression failure - prepared xacts
>
>
>
> Short answer:
>
>
Dave Page wrote:
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Andrew Dunstan
Sent: 14 July 2005 13:35
To: Tom Lane
Cc: PostgreSQL-development
Subject: Re: [HACKERS] windows regression failure - prepared xacts
ON a related note, we need
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Andrew Dunstan
> Sent: 14 July 2005 13:35
> To: Tom Lane
> Cc: PostgreSQL-development
> Subject: Re: [HACKERS] windows regression failure - prepared xacts
>
>
&
Tom Lane wrote:
Andrew Dunstan <[EMAIL PROTECTED]> writes:
further (anecdotal) data point: I have usually seen this after doing a
number of builds. Rebooting seems to cure the problem (and that's
happened today agin - I have just seen 2 builds work). Maybe some sort
of strange shmem corr
Andrew Dunstan <[EMAIL PROTECTED]> writes:
> further (anecdotal) data point: I have usually seen this after doing a
> number of builds. Rebooting seems to cure the problem (and that's
> happened today agin - I have just seen 2 builds work). Maybe some sort
> of strange shmem corruption?
Hmmm ..
further (anecdotal) data point: I have usually seen this after doing a
number of builds. Rebooting seems to cure the problem (and that's
happened today agin - I have just seen 2 builds work). Maybe some sort
of strange shmem corruption?
cheers
andrew
Tom Lane wrote:
Andrew Dunstan <[EMAI
Andrew Dunstan <[EMAIL PROTECTED]> writes:
> I never got a reply to this, but I am still seeing it from time to time
> - twice today in fact. Any suggestions?
I've been puzzled by that too. It seems to indicate that the syscache
inval message that the COMMIT should send is either not getting sen
I never got a reply to this, but I am still seeing it from time to time
- twice today in fact. Any suggestions?
cheers
andrew
Andrew Dunstan wrote:
I am consistently seeing the regression failure shown below on my
Windows machine. See
http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=lo
12 matches
Mail list logo
