Seeing failure on 8.1 as well.
BTW, I keep forwarding these, but is there any need? Are enough hackers on the
status change lists anyway?
/D
-Original Message-
From: PG Build Farm[EMAIL PROTECTED]
Sent: 18/03/06 02:13:19
To: [EMAIL PROTECTED][EMAIL PROTECTED], [EMAIL PROTECTED][EMAIL
On Mar 8, 2006, at 13:01 , Bruce Momjian wrote:
I have updated the /contrib and PL regression tests for
escape_string_warning. I can't test all the regressions but the build
farm will tell us soon enough.
I see 'em turning green :) Thanks, Bruce.
Michael Glaesemann
grzm myrealbox com
Michael Glaesemann wrote:
On Mar 8, 2006, at 13:01 , Bruce Momjian wrote:
I have updated the /contrib and PL regression tests for
escape_string_warning. I can't test all the regressions but the build
farm will tell us soon enough.
I see 'em turning green :) Thanks, Bruce.
Great.
-Original Message-
From: PG Build Farm
[mailto:[EMAIL PROTECTED]
Sent: 07 March 2006 02:18
To: [EMAIL PROTECTED];
[EMAIL PROTECTED]
Subject: PGBuildfarm member snake Branch HEAD Status changed
from OK to PLCheck failure
The PGBuildfarm member snake had the following
On Mar 7, 2006, at 17:48 , Dave Page wrote:
The PGBuildfarm member snake had the following event on branch HEAD:
Status changed from OK to PLCheck failure
The snapshot timestamp for the build that triggered this
notification is: 2006-03-07 02:00:00
The specs of this machine are:
OS:
Michael Glaesemann [EMAIL PROTECTED] writes:
This seems pretty widespread.
Try universal --- Bruce broke both contrib and PL regression tests
last night, by not updating them for the change of escape_string_warning
default.
regards, tom lane
Tom Lane wrote:
Michael Glaesemann [EMAIL PROTECTED] writes:
This seems pretty widespread.
Try universal --- Bruce broke both contrib and PL regression tests
last night, by not updating them for the change of escape_string_warning
default.
I have updated the /contrib and PL regression
And the fun continues :-)
-Original Message-
From: PG Build Farm
[mailto:[EMAIL PROTECTED]
Sent: 14 February 2006 02:16
To: [EMAIL PROTECTED]
Subject: PGBuildfarm member snake Branch HEAD Status changed
from Make failure to Contrib failure
The PGBuildfarm member snake had
Dave Page wrote:
And the fun continues :-)
-Original Message-
From: PG Build Farm
[mailto:[EMAIL PROTECTED]
Sent: 14 February 2006 02:16
To: [EMAIL PROTECTED]
Subject: PGBuildfarm member snake Branch HEAD Status changed
from Make failure to Contrib failure
The PGBuildfarm
-Original Message-
From: Mark Kirkwood [mailto:[EMAIL PROTECTED]
Sent: 14 February 2006 10:17
To: Dave Page
Cc: pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] FW: PGBuildfarm member snake Branch
HEAD Status changed from Make failure to Contrib failure
Oh dear - looks
Dave Page dpage@vale-housing.co.uk writes:
And the fun continues :-)
Info: resolving _MaxFSMPages by linking to __imp__MaxFSMPages (auto-import)
Fixed.
regards, tom lane
---(end of broadcast)---
TIP 5: don't forget to
Mark Kirkwood [EMAIL PROTECTED] writes:
Oh dear - looks like my pg_freespacemap patch is getting its Windows
testing :-(
Dave - are you able to try out the attached patch?
Already committed an equivalent patch before seeing your message ...
regards, tom lane
And another failure on Snake
/D
-Original Message-
From: PG Build Farm
[mailto:[EMAIL PROTECTED]
Sent: 13 February 2006 02:10
To: [EMAIL PROTECTED]
Subject: PGBuildfarm member snake Branch HEAD Status changed
from CVS-Unknown failure to Make failure
The PGBuildfarm
Hello,
That's caused by small error in recent implementation of dealing with
multi-line queries.
I already have sent the patch to pgsql-patches
Regards,
Sergey
On Mon, 13 Feb 2006, Dave Page wrote:
And another failure on Snake
/D
-Original Message-
From: PG
Just fixed in CVS. Thanks.
---
Dave Page wrote:
And another failure on Snake
/D
-Original Message-
From: PG Build Farm
[mailto:[EMAIL PROTECTED]
Sent: 13 February 2006 02:10
To: [EMAIL
How do people feel about having tabs displayed as 0x09? Should they be
a literal tab?
---
Teodor Sigaev wrote:
***
*** 2463,2469
a href=http://www.google.com/foo.bar.html; target=_blankYES nbsp;/a
Bruce Momjian pgman@candle.pha.pa.us writes:
How do people feel about having tabs displayed as 0x09? Should they be
a literal tab?
If they're a literal tab they'll mess up the formatting that we just so
painstakingly put in. I'd personally vote for \t rather than \x09, but
other than that I
Something broke snake again :-(. Looks like tsearch2 through the haze of
my Lemsip... I hate winter :-(
/D
-Original Message-
From: PG Build Farm
[mailto:[EMAIL PROTECTED]
Sent: 10 February 2006 02:20
To: [EMAIL PROTECTED];
[EMAIL PROTECTED]
Subject: PGBuildfarm member snake
On Feb 10, 2006, at 17:24 , Dave Page wrote:
Something broke snake again :-(. Looks like tsearch2 through the
haze of
my Lemsip... I hate winter :-(
Hope you feel better soon! I've been taking 1500 to 2000mg of vitamin
C daily to try to stay healthy.
As for snake, I can't offer much.
***
*** 2463,2469
a href=http://www.google.com/foo.bar.html; target=_blankYES nbsp;/a
ff-bg
script
! document.write(15);
/script
/body
/html
--- 2463,2469
a href=http://www.google.com/foo.bar.html; target=_blankYES nbsp;/a
ff-bg
script
!
On 2/10/06, Dave Page dpage@vale-housing.co.uk wrote:
Something broke snake again :-(. Looks like tsearch2 through the haze of
my Lemsip... I hate winter :-(
AFAIR the reason for different length of psql's '' header lines
was database encoding being UNICODE not SQL_ASCII. Can this be the
On 2/10/06, Marko Kreen [EMAIL PROTECTED] wrote:
On 2/10/06, Dave Page dpage@vale-housing.co.uk wrote:
Something broke snake again :-(. Looks like tsearch2 through the haze of
my Lemsip... I hate winter :-(
AFAIR the reason for different length of psql's '' header lines
was database
-Original Message-
From: Marko Kreen [mailto:[EMAIL PROTECTED]
Sent: 10 February 2006 15:07
To: Dave Page
Cc: pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] FW: PGBuildfarm member snake Branch
HEAD Status changed from OK to ContribCheck failure
On 2/10/06, Dave Page
Kreen [mailto:[EMAIL PROTECTED]
Sent: 10 February 2006 15:07
To: Dave Page
Cc: pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] FW: PGBuildfarm member snake Branch
HEAD Status changed from OK to ContribCheck failure
On 2/10/06, Dave Page dpage@vale-housing.co.uk wrote:
Something
Looks like the plperl changes hurt Snake :-(
C:/Perl/lib/CORE/win32iop.h:304:1: warning: kill redefined
In file included from ../../../src/include/c.h:821,
from ../../../src/include/postgres.h:48,
from SPI.xs:2:
../../../src/include/port.h:197:1: warning: this is
Looks like the tsearch2 update yesterday broke something :-(
Regards, Dave
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Sent: 09 November 2005 02:20
To: [EMAIL PROTECTED];
[EMAIL PROTECTED]
Subject: PGBuildfarm member snake Branch HEAD Status changed
Sorry, I'm working on it
Dave Page wrote:
Looks like the tsearch2 update yesterday broke something :-(
Regards, Dave
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Sent: 09 November 2005 02:20
To: [EMAIL PROTECTED];
[EMAIL PROTECTED]
Subject: PGBuildfarm
Andrew Dunstan [EMAIL PROTECTED] writes:
Alvaro Herrera wrote:
Here, the culprits are tfind() and tsearch(). These apparently aren't
portable enough, but they seem to exist on all other platforms. Maybe
we could come up with a replacement on Windows? Are there simple
btree/hash table
Looks like there more unprotable code in the recent changes to pgbench
:-(
Regards, Dave.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Sent: 30 September 2005 02:17
To: [EMAIL PROTECTED];
[EMAIL PROTECTED]
Subject: PGBuildfarm member snake Branch HEAD
On Fri, Sep 30, 2005 at 10:08:11AM +0100, Dave Page wrote:
Looks like there more unprotable code in the recent changes to pgbench
:-(
Here, the culprits are tfind() and tsearch(). These apparently aren't
portable enough, but they seem to exist on all other platforms. Maybe
we could come up
Alvaro Herrera wrote:
On Fri, Sep 30, 2005 at 10:08:11AM +0100, Dave Page wrote:
Looks like there more unprotable code in the recent changes to pgbench
:-(
Here, the culprits are tfind() and tsearch(). These apparently aren't
portable enough, but they seem to exist on all other
31 matches
Mail list logo
