Re: [HACKERS] rc1 or beta4?

[Simon Riggs]

On Wed, Aug 17, 2011 at 5:33 PM, Dave Page  wrote:

> That doesn't mean other things can't or shouldn't be fixed - just that
> they won't necessarily cause adjustment of the schedule to accomodate
> them.

+1

-- 
 Simon Riggs   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] rc1 or beta4?

[Tom Lane]

Dave Byrne  writes:
> I can confirm that the bug in pg_upgrade has been fixed with Bruce's patch
> in commit 2411fbdac448045a23eebf4f0dbfd5790ebad720

Thanks, I marked it resolved on the wiki page.

regards, tom lane

-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] rc1 or beta4?

[Dave Byrne]

On 08/17/2011 09:42 AM, Tom Lane wrote:


I think you're imagining a lot more structure than actually exists in
this project ;-).  Anybody can edit that page, and there's no necessary
consequence of something being written there.  It's just notes to help
us keep track of issues, not something graven on stone tablets.

The pg_upgrade thing is listed as a beta blocker because I put it there
--- but that's just my opinion.  If it had proven hard to fix we might
have concluded that we wouldn't let it block a beta release.

If the plpython thing is a new crash that didn't exist before 9.1,
my feeling is that it's a blocker.

regards, tom lane



I can confirm that the bug in pg_upgrade has been fixed with Bruce's patch
in commit 2411fbdac448045a23eebf4f0dbfd5790ebad720

Thanks
Dave Byrne


--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] rc1 or beta4?

[Tom Lane]

Thom Brown  writes:
> On 17 August 2011 16:56, Jan Urbański  wrote:
>> On 17/08/11 17:50, Thom Brown wrote:
>>> It's not listed as a beta-blocker yet.  I take it that it should?

>> Oh, in the wiki? I don't know, it is a segfault-causing bug, but all I
>> wanted was to draw some attention in case the people wrapping the
>> release missed that thread.

> It was my understanding that the only things which can prevent a new beta or
> release candidate are listed on the wiki (
> http://wiki.postgresql.org/wiki/PostgreSQL_9.1_Open_Items).  There's only
> one item on the list now, and I think even that has probably been fixed.  If
> it's not on there, I guess it hasn't yet been considered to be something
> which can block a release.  Since it's not even listed as a non-blocker
> either, I don't think it's been reviewed in this context.

I think you're imagining a lot more structure than actually exists in
this project ;-).  Anybody can edit that page, and there's no necessary
consequence of something being written there.  It's just notes to help
us keep track of issues, not something graven on stone tablets.

The pg_upgrade thing is listed as a beta blocker because I put it there
--- but that's just my opinion.  If it had proven hard to fix we might
have concluded that we wouldn't let it block a beta release.

If the plpython thing is a new crash that didn't exist before 9.1,
my feeling is that it's a blocker.

regards, tom lane

-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] rc1 or beta4?

[Dave Page]

On Wed, Aug 17, 2011 at 5:16 PM, Thom Brown  wrote:
> On 17 August 2011 16:56, Jan Urbański  wrote:
>>
>> On 17/08/11 17:50, Thom Brown wrote:
>> > On 17 August 2011 16:47, Jan Urbański  wrote:
>> >
>> >> On 17/08/11 15:00, Dave Page wrote:
>> >>> The current plan (or, the last one I recall) is to push another 9.1
>> >>> release tomorrow, for Monday release. Are we going with beta4 or rc1?
>> >>
>> >> Sorry to butt in, but it would probably be good to include fixes for
>> >> the
>> >> two segfault plpython bugs[1] before wrapping up the release.
>> >>
>> >
>> > It's not listed as a beta-blocker yet.  I take it that it should?
>>
>> Oh, in the wiki? I don't know, it is a segfault-causing bug, but all I
>> wanted was to draw some attention in case the people wrapping the
>> release missed that thread.
>
> It was my understanding that the only things which can prevent a new beta or
> release candidate are listed on the wiki
> (http://wiki.postgresql.org/wiki/PostgreSQL_9.1_Open_Items).  There's only
> one item on the list now, and I think even that has probably been fixed.  If
> it's not on there, I guess it hasn't yet been considered to be something
> which can block a release.  Since it's not even listed as a non-blocker
> either, I don't think it's been reviewed in this context.

That doesn't mean other things can't or shouldn't be fixed - just that
they won't necessarily cause adjustment of the schedule to accomodate
them.

-- 
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] rc1 or beta4?

[Thom Brown]

On 17 August 2011 16:56, Jan Urbański  wrote:

> On 17/08/11 17:50, Thom Brown wrote:
> > On 17 August 2011 16:47, Jan Urbański  wrote:
> >
> >> On 17/08/11 15:00, Dave Page wrote:
> >>> The current plan (or, the last one I recall) is to push another 9.1
> >>> release tomorrow, for Monday release. Are we going with beta4 or rc1?
> >>
> >> Sorry to butt in, but it would probably be good to include fixes for the
> >> two segfault plpython bugs[1] before wrapping up the release.
> >>
> >
> > It's not listed as a beta-blocker yet.  I take it that it should?
>
> Oh, in the wiki? I don't know, it is a segfault-causing bug, but all I
> wanted was to draw some attention in case the people wrapping the
> release missed that thread.
>

It was my understanding that the only things which can prevent a new beta or
release candidate are listed on the wiki (
http://wiki.postgresql.org/wiki/PostgreSQL_9.1_Open_Items).  There's only
one item on the list now, and I think even that has probably been fixed.  If
it's not on there, I guess it hasn't yet been considered to be something
which can block a release.  Since it's not even listed as a non-blocker
either, I don't think it's been reviewed in this context.

-- 
Thom Brown
Twitter: @darkixion
IRC (freenode): dark_ixion
Registered Linux user: #516935

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Re: [HACKERS] rc1 or beta4?

[Jan Urbański]

On 17/08/11 17:50, Thom Brown wrote:
> On 17 August 2011 16:47, Jan Urbański  wrote:
> 
>> On 17/08/11 15:00, Dave Page wrote:
>>> The current plan (or, the last one I recall) is to push another 9.1
>>> release tomorrow, for Monday release. Are we going with beta4 or rc1?
>>
>> Sorry to butt in, but it would probably be good to include fixes for the
>> two segfault plpython bugs[1] before wrapping up the release.
>>
> 
> It's not listed as a beta-blocker yet.  I take it that it should?

Oh, in the wiki? I don't know, it is a segfault-causing bug, but all I
wanted was to draw some attention in case the people wrapping the
release missed that thread.

Jan

-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] rc1 or beta4?

[Dave Page]

On Wed, Aug 17, 2011 at 4:47 PM, Jan Urbański  wrote:
> On 17/08/11 15:00, Dave Page wrote:
>> The current plan (or, the last one I recall) is to push another 9.1
>> release tomorrow, for Monday release. Are we going with beta4 or rc1?
>
> Sorry to butt in, but it would probably be good to include fixes for the
> two segfault plpython bugs[1] before wrapping up the release.

And Ashesh's fix for building against ActiveState Python 3.2:
http://archives.postgresql.org/pgsql-hackers/2011-08/msg00836.php.
Care to review that one? :-)



-- 
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] rc1 or beta4?

[Thom Brown]

On 17 August 2011 16:47, Jan Urbański  wrote:

> On 17/08/11 15:00, Dave Page wrote:
> > The current plan (or, the last one I recall) is to push another 9.1
> > release tomorrow, for Monday release. Are we going with beta4 or rc1?
>
> Sorry to butt in, but it would probably be good to include fixes for the
> two segfault plpython bugs[1] before wrapping up the release.
>

It's not listed as a beta-blocker yet.  I take it that it should?

-- 
Thom Brown
Twitter: @darkixion
IRC (freenode): dark_ixion
Registered Linux user: #516935

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Re: [HACKERS] rc1 or beta4?

[Jan Urbański]

On 17/08/11 15:00, Dave Page wrote:
> The current plan (or, the last one I recall) is to push another 9.1
> release tomorrow, for Monday release. Are we going with beta4 or rc1?

Sorry to butt in, but it would probably be good to include fixes for the
two segfault plpython bugs[1] before wrapping up the release.

Cheers,
Jan

[1] http://archives.postgresql.org/message-id/4e4bcd52.90...@wulczer.org

-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] rc1 or beta4?

[Pavel Golub]

Hello, Dave.

You wrote:

DP> The current plan (or, the last one I recall) is to push another 9.1
DP> release tomorrow, for Monday release. Are we going with beta4 or rc1?

+1 for RC1

DP> -- 
DP> Dave Page
DP> Blog: http://pgsnake.blogspot.com
DP> Twitter: @pgsnake

DP> EnterpriseDB UK: http://www.enterprisedb.com
DP> The Enterprise PostgreSQL Company




-- 
With best wishes,
 Pavel  mailto:pa...@gf.microolap.com


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] rc1 or beta4?

[Tom Lane]

Dave Page  writes:
>>> Are we going with beta4 or rc1?

> In Tom's final email to the -core thread he mentions I see now that he
> did say RC1. I thought we were voting on the date though (not that I
> have a problem with it being RC1).

Well, if this one's not ready to be an RC then I think we can forget
about pushing out a final during September ...

regards, tom lane

-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] rc1 or beta4?

[Dave Page]

2011/8/17 Devrim GÜNDÜZ :
> On Wed, 2011-08-17 at 14:00 +0100, Dave Page wrote:
>> Are we going with beta4 or rc1?
>
> RC1:
>
> http://archives.postgresql.org/message-id/19869.1312298...@sss.pgh.pa.us

In Tom's final email to the -core thread he mentions I see now that he
did say RC1. I thought we were voting on the date though (not that I
have a problem with it being RC1).

-- 
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] rc1 or beta4?

[Devrim GÜNDÜZ]

On Wed, 2011-08-17 at 14:00 +0100, Dave Page wrote:
> Are we going with beta4 or rc1?

RC1:

http://archives.postgresql.org/message-id/19869.1312298...@sss.pgh.pa.us

Regards,
-- 
Devrim GÜNDÜZ
Principal Systems Engineer @ EnterpriseDB: http://www.enterprisedb.com
PostgreSQL Danışmanı/Consultant, Red Hat Certified Engineer
Community: devrim~PostgreSQL.org, devrim.gunduz~linux.org.tr
http://www.gunduz.org  Twitter: http://twitter.com/devrimgunduz


signature.asc
Description: This is a digitally signed message part

Re: [HACKERS] RC1 / Beta4?

[Martin Atukunda]

Now I understand.

At the day job we were being pushed hard to have some tests completed
before or on 30th June. The major push behind this was a French man!
:)

And yes, he's off for the next 2-3 weeks, and we did complete the tests!

- Martin -

On Sat, Jul 30, 2011 at 12:44 PM, Dave Page  wrote:
>
>
> On Saturday, July 30, 2011, Lou Picciano  wrote:
>> I think it's just that the Europeans - wisely - have a habit of taking
>> these long summer vacations (!)
>> They also tend to be taller and better-looking than the rest of us, and
>> have better food and wine.
>> :)  Lou
>
> This would be one of those few moments when Brits admit to being part of
> Europe...
>
> :-)
>
> Back on topic, there are people away next week who we rely on for releases,
> and both I and the QA team who test the installers will be unavailable the
> following week. After that the majority of people we need for a release
> should be around I think.
>
> --
> Dave Page
> Blog: http://pgsnake.blogspot.com
> Twitter: @pgsnake
>
> EnterpriseDB UK: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>
>

-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] RC1 / Beta4?

[Dave Page]

On Saturday, July 30, 2011, Lou Picciano  wrote:
> I think it's just that the Europeans - wisely - have a habit of taking
these long summer vacations (!)
> They also tend to be taller and better-looking than the rest of us, and
have better food and wine.
> :)  Lou

This would be one of those few moments when Brits admit to being part of
Europe...

:-)

Back on topic, there are people away next week who we rely on for releases,
and both I and the QA team who test the installers will be unavailable the
following week. After that the majority of people we need for a release
should be around I think.

-- 
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Re: [HACKERS] RC1 / Beta4?

[Lou Picciano]

I think it's just that the Europeans - wisely - have a habit of taking these 
long summer vacations (!) 


They also tend to be taller and better-looking than the rest of us, and have 
better food and wine. 


:) Lou 

- Original Message -
From: "Martin Atukunda"  
To: "Joshua Berkus"  
Cc: "postgres hackers"  
Sent: Saturday, July 30, 2011 4:48:03 AM 
Subject: Re: [HACKERS] RC1 / Beta4? 

Hi All, 

Just a quick question because I don't get the reference to the 
europeans. What do they have to do with the final release in August? 

:) 

Thanks, 

- Martin - 

On Sat, Jul 30, 2011 at 2:58 AM, Joshua Berkus  wrote: 
> All, 
> 
> Where are we on RC1 or Beta4 for PostgreSQL 9.1? 
> 
> While I know we're doing going to do a final release in August due to the 
> europeans, it would be nice to move things along before then. There don't 
> seem to be any blockers open. 
> 
> -- 
> Josh Berkus 
> PostgreSQL Experts Inc. 
> http://pgexperts.com 
> San Francisco 
> 
> -- 
> Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) 
> To make changes to your subscription: 
> http://www.postgresql.org/mailpref/pgsql-hackers 
> 

-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) 
To make changes to your subscription: 
http://www.postgresql.org/mailpref/pgsql-hackers 

Re: [HACKERS] RC1 / Beta4?

[Martin Atukunda]

Hi All,

Just a quick question because I don't get the reference to the
europeans. What do they have to do with the final release in August?

:)

Thanks,

- Martin -

On Sat, Jul 30, 2011 at 2:58 AM, Joshua Berkus  wrote:
> All,
>
> Where are we on RC1 or Beta4 for PostgreSQL 9.1?
>
> While I know we're doing going to do a final release in August due to the 
> europeans, it would be nice to move things along before then.  There don't 
> seem to be any blockers open.
>
> --
> Josh Berkus
> PostgreSQL Experts Inc.
> http://pgexperts.com
> San Francisco
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>

-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] rc1 tarball contains partially outdated/missing man pages

[Peter Eisentraut]

On Friday 19 June 2009 19:12:50 Tom Lane wrote:
> Well, at the time I thought that WITH would only be a sub-clause of
> SELECT.  The idea that we might allow it to be attached to INSERT etc
> causes me to revise my opinion a bit.  Do you have a preference one
> way or the other about how to do this?

I can't really imagine it right now, but when INSERT actually supports this, 
I'm sure we can come up with something.  At the moment I'm concentrating on 
tweaking it so that the current setup works in 8.4.  Which I think it does 
now, but it would be good if others could give the man pages themselves and 
their installation some extra testing in rc2.

-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] rc1 tarball contains partially outdated/missing man pages

[Tom Lane]

Peter Eisentraut  writes:
> On Thursday 18 June 2009 23:15:53 Tom Lane wrote:
>> BTW, as far as that particular point goes: maybe we could fix the tools
>> issues underlying this, but I'm tempted to think that it's not worth the
>> trouble, because making these man pages be aliases for SELECT is just
>> the Wrong Thing anyway.  I think we should just split them off and have
>> them be documented as separate top-level reference pages.

> Umm, the reason why it is that way now is that you did not want them to be 
> separate top-level man pages:
> http://archives.postgresql.org/message-id/19886.1226171...@sss.pgh.pa.us

Well, at the time I thought that WITH would only be a sub-clause of
SELECT.  The idea that we might allow it to be attached to INSERT etc
causes me to revise my opinion a bit.  Do you have a preference one
way or the other about how to do this?

regards, tom lane

-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] rc1 tarball contains partially outdated/missing man pages

[Peter Eisentraut]

On Thursday 18 June 2009 23:15:53 Tom Lane wrote:
> I wrote:
> > One thing I notice is that the "table" and "with" entries are not coming
> > out as intended.  The file names are all caps:
> >
> > -rw-r--r--   1 tglusers   18 Jun 12 01:37 WITH.7
> > -rw-r--r--   1 tglusers   18 Jun 12 01:37 TABLE.7
> >
> > and the content surely isn't what was meant:
> >
> > $ more TABLE.7
> > .so man7/SELECT.7
> > $ more WITH.7
> > .so man7/SELECT.7

The content is pretty much what was meant, except that the case is wrong.  
Typing "man SELECT" will find a lower case select.7 man page, but the .so 
mechanism apparently doesn't.  The simple fix is to convert all man page names 
to upper case, which is the default in the tools anyway.

> BTW, as far as that particular point goes: maybe we could fix the tools
> issues underlying this, but I'm tempted to think that it's not worth the
> trouble, because making these man pages be aliases for SELECT is just
> the Wrong Thing anyway.  I think we should just split them off and have
> them be documented as separate top-level reference pages.

Umm, the reason why it is that way now is that you did not want them to be 
separate top-level man pages:

http://archives.postgresql.org/message-id/19886.1226171...@sss.pgh.pa.us


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] rc1 tarball contains partially outdated/missing man pages

[Peter Eisentraut]

On Thursday 18 June 2009 22:48:53 Tom Lane wrote:
> Peter Eisentraut  writes:
> > I noticed that the rc1 tarball does not contain man pages for
> > CREATE/ALTER/DROP FOREIGN DATA WRAPPER/SERVER/USER MAPPING.
>
> Just eyeballing the files, I notice that those ref pages seem not
> to contain this boilerplate:
>
>   7
>
> which is mostly(?) present in others.  Maybe the cause?

Great find. -- Fixed.

-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] rc1 tarball contains partially outdated/missing man pages

[Tom Lane]

I wrote:
> One thing I notice is that the "table" and "with" entries are not coming
> out as intended.  The file names are all caps:

> -rw-r--r--   1 tglusers   18 Jun 12 01:37 WITH.7
> -rw-r--r--   1 tglusers   18 Jun 12 01:37 TABLE.7

> and the content surely isn't what was meant:

> $ more TABLE.7
> .so man7/SELECT.7
> $ more WITH.7
> .so man7/SELECT.7

BTW, as far as that particular point goes: maybe we could fix the tools
issues underlying this, but I'm tempted to think that it's not worth the
trouble, because making these man pages be aliases for SELECT is just
the Wrong Thing anyway.  I think we should just split them off and have
them be documented as separate top-level reference pages.  Doing that
for TABLE is clearly fairly sensible; and as for WITH, the current
approach is going to fail miserably anyhow as soon as we allow WITH
to be prefixed to INSERT/UPDATE/DELETE.  Which is something that was
already requested, and I see no semantic or implementation reason not
to allow (in 8.5 of course, not now).  So I'm thinking we make a man
page for WITH as such, and cross-reference it from SELECT, moving the
current discussion of CTEs over.

regards, tom lane

-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] rc1 tarball contains partially outdated/missing man pages

[Tom Lane]

Peter Eisentraut  writes:
> I noticed that the rc1 tarball does not contain man pages for 
> CREATE/ALTER/DROP FOREIGN DATA WRAPPER/SERVER/USER MAPPING.

Just eyeballing the files, I notice that those ref pages seem not
to contain this boilerplate:

  7

which is mostly(?) present in others.  Maybe the cause?

regards, tom lane

-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] rc1 tarball contains partially outdated/missing man pages

[Tom Lane]

Peter Eisentraut  writes:
> Can someone check, or remind me how the man pages end up in the tarball?

They're supposed to be built on the fly, and the file dates in the rc1
tarball do appear to match the time of tarball building.  Do you get
what you expect if you build the man pages locally?

One thing I notice is that the "table" and "with" entries are not coming
out as intended.  The file names are all caps:

-rw-r--r--   1 tglusers   18 Jun 12 01:37 WITH.7
-rw-r--r--   1 tglusers   18 Jun 12 01:37 TABLE.7

and the content surely isn't what was meant:

$ more TABLE.7
.so man7/SELECT.7
$ more WITH.7
.so man7/SELECT.7

regards, tom lane

-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] rc1 packaged ...

[Marc G. Fournier]

'k, I'm upgraded for 1.79 and RC3 ...
On Tue, 21 Dec 2004, Peter Eisentraut wrote:
Marc G. Fournier wrote:
'k, I'm about to screw up rc2 for this too ... FreeBSD ports is
'stuck' at 1.78 ...
Well, file a bug to get it updated?
just went to
http://sourceforge.net/projects/docbook, and there are two '1.79's
... do both need to be installed, or just one of them?
The second one is the documentation.  You don't need that unless you
plan to read it.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/

Marc G. Fournier   Hub.Org Networking Services (http://www.hub.org)
Email: [EMAIL PROTECTED]   Yahoo!: yscrappy  ICQ: 7615664
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
 subscribe-nomail command to [EMAIL PROTECTED] so that your
 message can get through to the mailing list cleanly

Re: [HACKERS] rc1 packaged ...

[Peter Eisentraut]

Marc G. Fournier wrote:
> 'k, I'm about to screw up rc2 for this too ... FreeBSD ports is
> 'stuck' at 1.78 ...

Well, file a bug to get it updated?

> just went to 
> http://sourceforge.net/projects/docbook, and there are two '1.79's
> ... do both need to be installed, or just one of them?

The second one is the documentation.  You don't need that unless you 
plan to read it.

-- 
Peter Eisentraut
http://developer.postgresql.org/~petere/

---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])

Re: [HACKERS] rc1 packaged ...

[Marc G. Fournier]

On Mon, 20 Dec 2004, Bruce Momjian wrote:
Marc G. Fournier wrote:
On Tue, 14 Dec 2004, Peter Eisentraut wrote:
Am Samstag, 4. Dezember 2004 00:12 schrieb Marc G. Fournier:
look her over ... I forced a sync to the ftp.postgresql.org server, so its
available there ... will announce later this evening baring any 'its
broken' commends ;)
You are building the documentation with old stylesheets.  Please use version
1.79, as announced some time ago on pgsql-docs.  Let me know if you have
problems, but we should get this fixed for the release.
'k, I'm about to screw up rc2 for this too ... FreeBSD ports is 'stuck' at
1.78 ... just went to http://sourceforge.net/projects/docbook, and there
are two '1.79's ... do both need to be installed, or just one of them?
I'm going to build the package right now, but if you can let me know which
(or both) need to be installed, I'll get right on that ...
Marc, I assume Peter is asleep right now in Germany.  :-)
Yup, which is why I'm goin to fix this for release, instead of rc2 :)

Marc G. Fournier   Hub.Org Networking Services (http://www.hub.org)
Email: [EMAIL PROTECTED]   Yahoo!: yscrappy  ICQ: 7615664
---(end of broadcast)---
TIP 6: Have you searched our list archives?
  http://archives.postgresql.org

Re: [HACKERS] rc1 packaged ...

[Bruce Momjian]

Marc G. Fournier wrote:
> On Tue, 14 Dec 2004, Peter Eisentraut wrote:
> 
> > Am Samstag, 4. Dezember 2004 00:12 schrieb Marc G. Fournier:
> >> look her over ... I forced a sync to the ftp.postgresql.org server, so its
> >> available there ... will announce later this evening baring any 'its
> >> broken' commends ;)
> >
> > You are building the documentation with old stylesheets.  Please use version
> > 1.79, as announced some time ago on pgsql-docs.  Let me know if you have
> > problems, but we should get this fixed for the release.
> 
> 'k, I'm about to screw up rc2 for this too ... FreeBSD ports is 'stuck' at 
> 1.78 ... just went to http://sourceforge.net/projects/docbook, and there 
> are two '1.79's ... do both need to be installed, or just one of them?
> 
> I'm going to build the package right now, but if you can let me know which 
> (or both) need to be installed, I'll get right on that ...

Marc, I assume Peter is asleep right now in Germany.  :-)

-- 
  Bruce Momjian|  http://candle.pha.pa.us
  [EMAIL PROTECTED]   |  (610) 359-1001
  +  If your life is a hard drive, |  13 Roberts Road
  +  Christ can be your backup.|  Newtown Square, Pennsylvania 19073

---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])

Re: [HACKERS] rc1 packaged ...

[Marc G. Fournier]

On Tue, 14 Dec 2004, Peter Eisentraut wrote:
Am Samstag, 4. Dezember 2004 00:12 schrieb Marc G. Fournier:
look her over ... I forced a sync to the ftp.postgresql.org server, so its
available there ... will announce later this evening baring any 'its
broken' commends ;)
You are building the documentation with old stylesheets.  Please use version
1.79, as announced some time ago on pgsql-docs.  Let me know if you have
problems, but we should get this fixed for the release.
'k, I'm about to screw up rc2 for this too ... FreeBSD ports is 'stuck' at 
1.78 ... just went to http://sourceforge.net/projects/docbook, and there 
are two '1.79's ... do both need to be installed, or just one of them?

I'm going to build the package right now, but if you can let me know which 
(or both) need to be installed, I'll get right on that ...


Marc G. Fournier   Hub.Org Networking Services (http://www.hub.org)
Email: [EMAIL PROTECTED]   Yahoo!: yscrappy  ICQ: 7615664
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
  http://www.postgresql.org/docs/faqs/FAQ.html

Re: [HACKERS] rc1 packaged ...

[Peter Eisentraut]

Am Samstag, 4. Dezember 2004 00:12 schrieb Marc G. Fournier:
> look her over ... I forced a sync to the ftp.postgresql.org server, so its
> available there ... will announce later this evening baring any 'its
> broken' commends ;)

You are building the documentation with old stylesheets.  Please use version 
1.79, as announced some time ago on pgsql-docs.  Let me know if you have 
problems, but we should get this fixed for the release.

-- 
Peter Eisentraut
http://developer.postgresql.org/~petere/

---(end of broadcast)---
TIP 6: Have you searched our list archives?

   http://archives.postgresql.org

Re: [HACKERS] rc1 packaged ...

[Tom Lane]

"Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> look her over ... I forced a sync to the ftp.postgresql.org server, so its 
> available there ... will announce later this evening baring any 'its 
> broken' commends ;)

Tarball looks alright to me.

regards, tom lane

---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings

Re: [HACKERS] RC1 on AIX - Some Anti-results

[Tom Lane]

Christopher Browne <[EMAIL PROTECTED]> writes:
> This _seems_ a cosmetic difference, or am I way wrong?

I think you can ignore it.  It's odd that your setup seems to support
minus zero (else there'd be more diffs) but doesn't get the right answer
for this single computation.  Still, it's basically a roundoff issue,
and as such a legitimate platform-specific behavior.

regards, tom lane

---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]

Re: [HACKERS] RC1 on AIX - working thus far

[Peter Eisentraut]

Christopher Browne writes:

> I'm afraid I hadn't seen another AIX report; this may replicate other reports...

See http://developer.postgresql.org/docs/postgres/supported-platforms.html
for a list of platforms that have been verified with 7.4.
(Linux/Playstation, Linux/hppa, and UnixWare will be added shortly.)

-- 
Peter Eisentraut   [EMAIL PROTECTED]


---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster

Re: [HACKERS] RC1 on AIX - working thus far

[Christopher Browne]

Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Christopher Browne writes:
>
>> bash-2.05a$ uname -a
>> AIX ibm-db 1 5 000CD13A4C00
>
> We already have a report for AIX.  Were you trying to indicate that this
> is a different variant thereof?

I'm afraid I hadn't seen another AIX report; this may replicate other reports...

I don't think I have seen an RC1 report on Solaris 8 yet, though I may
be wrong; if there isn't one, here's one...

 conversion   ... ok
 truncate ... ok
 alter_table  ... ok
 sequence ... ok
 polymorphism ... ok
 stats... ok
== shutting down postmaster   ==

==
 All 93 tests passed. 
==

make[2]: Leaving directory `/disk3/OXRS/postgresql-7.4RC1/src/test/regress'
make[1]: Leaving directory `/disk3/OXRS/postgresql-7.4RC1/src/test'
[EMAIL PROTECTED] /disk3/OXRS/postgresql-7.4RC1 > uname -a
SunOS ringo 5.8 Generic_108528-17 sun4u sparc SUNW,Ultra-4
[EMAIL PROTECTED] /disk3/OXRS/postgresql-7.4RC1 > 
-- 
let name="cbbrowne" and tld="libertyrms.info" in String.concat "@" [name;tld];;

Christopher Browne
(416) 646 3304 x124 (land)

---(end of broadcast)---
TIP 6: Have you searched our list archives?

   http://archives.postgresql.org

Re: [HACKERS] RC1 on AIX - working thus far

[Peter Eisentraut]

Christopher Browne writes:

> bash-2.05a$ uname -a
> AIX ibm-db 1 5 000CD13A4C00

We already have a report for AIX.  Were you trying to indicate that this
is a different variant thereof?

-- 
Peter Eisentraut   [EMAIL PROTECTED]


---(end of broadcast)---
TIP 6: Have you searched our list archives?

   http://archives.postgresql.org

Re: [PORTS] Geometry test on NetBSD (was Re: [HACKERS] RC1?)

[Henry B. Hotz]

At 1:51 PM -0500 11/20/02, Tom Lane wrote:

Patrick Welche <[EMAIL PROTECTED]> writes:

 On Wed, Nov 20, 2002 at 01:21:47PM -0500, Tom Lane wrote:

 Ah-hah, so it is a version issue --- we could make the resultmap line
 something like
 geometry/.*-netbsd1.[0-5]=geometry-positive-zeros



 NetBSD/i386-1.6H i386-unknown-netbsdelf1.6H (checked 7.3rc1)
 NetBSD/acorn32-1.6K  arm-unknown-netbsdelf1.6K  (still building 7.3rc1)


Hm, is that "elf" always there?  I'm a little uncomfortable with making
the pattern be
	geometry/.*-netbsd.*1.[0-5]=geometry-positive-zeros
as this seems way too lax ...


A version like 1.6[A-Z] is a -current, not a release version from in 
between 1.5.x and 1.6.

Different NetBSD ports have converted to elf at different times and 
not all ports are using elf even with 1.6 released.
--
The opinions expressed in this message are mine,
not those of Caltech, JPL, NASA, or the US Government.
[EMAIL PROTECTED], or [EMAIL PROTECTED]

---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
   (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])

Re: [PORTS] Geometry test on NetBSD (was Re: [HACKERS] RC1?)

[Henry B. Hotz]

At 1:15 AM -0500 11/20/02, Tom Lane wrote:

Bruce Momjian <[EMAIL PROTECTED]> writes:

 Tom, can you clarify why -0 is valid.


The IEEE spec absolutely thinks that -0 and +0 are distinct entities.
I don't remember why, at one in the morning ... but if you insist I'm
sure that plenty sufficient numerical-analysis reasons can be produced.
The guys who wrote that spec knew what they were doing (that's why it's
been adopted so universally).


It's so that 1/(1/-infinity) == -infinity.  There are probably other 
reasons as well.

I'm just guessing here, but it's possible NetBSD acquired the bug by 
trying to be functional on non-IEEE hardware.  I hope that whoever 
found the problem (I don't see that in this thread) filed a bug 
report with NetBSD.
--
The opinions expressed in this message are mine,
not those of Caltech, JPL, NASA, or the US Government.
[EMAIL PROTECTED], or [EMAIL PROTECTED]

---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster

Re: [HACKERS] RC1? AIX 4.2.1.0 (fwd)

[Samuel A Horwitz]

Sorry forgot to include that I had to add -lssl and -lcrypto ti the libpq 
line in Makefile.global.in in the src directory to get ecpg to link

as follows

286c286
< libpq = -L$(libpq_builddir) -lpq
---
> libpq = -L$(libpq_builddir) -lpq -lssl -lcrypto


[EMAIL PROTECTED] (Samuel A Horwitz)


-- Forwarded message --
Date: Mon, 25 Nov 2002 08:45:46 -0500 (EST)
From: Samuel A Horwitz <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: [HACKERS] RC1? AIX 4.2.1.0 

system = powerpc-ibm-aix4.2.1.0 


configure command 

env CC=gcc ./configure --with-maxbackends=1024 --with-openssl=/usr/local/ssl 
--enable-syslog --enable-odbc --disable-nls

gmake check output file


regression.out
--

parallel group (13 tests):  text varchar oid int2 char boolean float4 int4 name int8 
float8 bit numeric
 boolean  ... ok
 char ... ok
 name ... ok
 varchar  ... ok
 text ... ok
 int2 ... ok
 int4 ... ok
 int8 ... ok
 oid  ... ok
 float4   ... ok
 float8   ... ok
 bit  ... ok
 numeric  ... ok
test strings  ... ok
test numerology   ... ok
parallel group (20 tests):  lseg date path circle polygon box point time timetz 
tinterval abstime interval reltime comments inet timestamptz timestamp type_sanity 
opr_sanity oidjoins
 point... ok
 lseg ... ok
 box  ... ok
 path ... ok
 polygon  ... ok
 circle   ... ok
 date ... ok
 time ... ok
 timetz   ... ok
 timestamp... ok
 timestamptz  ... ok
 interval ... ok
 abstime  ... ok
 reltime  ... ok
 tinterval... ok
 inet ... ok
 comments ... ok
 oidjoins ... ok
 type_sanity  ... ok
 opr_sanity   ... ok
test geometry ... FAILED
test horology ... ok
test insert   ... ok
test create_function_1... ok
test create_type  ... ok
test create_table ... ok
test create_function_2... ok
test copy ... ok
parallel group (7 tests):  create_aggregate create_operator triggers vacuum inherit 
constraints create_misc
 constraints  ... ok
 triggers ... ok
 create_misc  ... ok
 create_aggregate ... ok
 create_operator  ... ok
 inherit  ... ok
 vacuum   ... ok
parallel group (2 tests):  create_view create_index
 create_index ... ok
 create_view  ... ok
test sanity_check ... ok
test errors   ... ok
test select   ... ok
parallel group (16 tests):  select_distinct_on select_into select_having transactions 
select_distinct random subselect portals arrays union select_implicit case aggregates 
hash_index join btree_index
 select_into  ... ok
 select_distinct  ... ok
 select_distinct_on   ... ok
 select_implicit  ... ok
 select_having... ok
 subselect... ok
 union... ok
 case ... ok
 join ... ok
 aggregates   ... ok
 transactions ... ok
 random   ... ok
 portals  ... ok
 arrays   ... ok
 btree_index  ... ok
 hash_index   ... ok
test privileges   ... ok
test misc ... ok
parallel group (5 tests):  portals_p2 cluster rules select_views foreign_key
 select_views ... ok
 portals_p2   ... ok
 rules... ok
 foreign_key  ... ok
 cluster  ... ok
parallel group (11 tests):  limit truncate temp copy2 domain rangefuncs conversion 
prepare without_oid plpgsql alter_table
 limit... ok
 plpgsql  ... ok
 copy2... ok
 temp ... ok
 domain   ... ok
 rangefuncs   ... ok
 prepare  ... ok
 without_oid  ... ok
 conversion   ... ok
 truncate ... ok
 alter_table  ... ok


regression.diffs
-


*** ./expected/geometry-powerpc-aix4.outTue Sep 12 17:07:16 2000
--- ./results/geometry.out  Thu Nov 21 21:46:01 2002
***
*** 114,120 
  | (5.1,34.5) | [(1,2),(3,4)] | (3,4)
  | (-5,-12)   | [(1,2),(3,4)] | (1,2)
  | (10,10)| [(1,2),(3,4)] | (3,4)
! | (0,0)  | [(0,0),(6,6)] | (0,0)
  

Re: [HACKERS] RC1? AIX 4.2.1.0

[Samuel A Horwitz]

system = powerpc-ibm-aix4.2.1.0 


configure command 

env CC=gcc ./configure --with-maxbackends=1024 --with-openssl=/usr/local/ssl 
--enable-syslog --enable-odbc --disable-nls

gmake check output file


regression.out
--

parallel group (13 tests):  text varchar oid int2 char boolean float4 int4 name int8 
float8 bit numeric
 boolean  ... ok
 char ... ok
 name ... ok
 varchar  ... ok
 text ... ok
 int2 ... ok
 int4 ... ok
 int8 ... ok
 oid  ... ok
 float4   ... ok
 float8   ... ok
 bit  ... ok
 numeric  ... ok
test strings  ... ok
test numerology   ... ok
parallel group (20 tests):  lseg date path circle polygon box point time timetz 
tinterval abstime interval reltime comments inet timestamptz timestamp type_sanity 
opr_sanity oidjoins
 point... ok
 lseg ... ok
 box  ... ok
 path ... ok
 polygon  ... ok
 circle   ... ok
 date ... ok
 time ... ok
 timetz   ... ok
 timestamp... ok
 timestamptz  ... ok
 interval ... ok
 abstime  ... ok
 reltime  ... ok
 tinterval... ok
 inet ... ok
 comments ... ok
 oidjoins ... ok
 type_sanity  ... ok
 opr_sanity   ... ok
test geometry ... FAILED
test horology ... ok
test insert   ... ok
test create_function_1... ok
test create_type  ... ok
test create_table ... ok
test create_function_2... ok
test copy ... ok
parallel group (7 tests):  create_aggregate create_operator triggers vacuum inherit 
constraints create_misc
 constraints  ... ok
 triggers ... ok
 create_misc  ... ok
 create_aggregate ... ok
 create_operator  ... ok
 inherit  ... ok
 vacuum   ... ok
parallel group (2 tests):  create_view create_index
 create_index ... ok
 create_view  ... ok
test sanity_check ... ok
test errors   ... ok
test select   ... ok
parallel group (16 tests):  select_distinct_on select_into select_having transactions 
select_distinct random subselect portals arrays union select_implicit case aggregates 
hash_index join btree_index
 select_into  ... ok
 select_distinct  ... ok
 select_distinct_on   ... ok
 select_implicit  ... ok
 select_having... ok
 subselect... ok
 union... ok
 case ... ok
 join ... ok
 aggregates   ... ok
 transactions ... ok
 random   ... ok
 portals  ... ok
 arrays   ... ok
 btree_index  ... ok
 hash_index   ... ok
test privileges   ... ok
test misc ... ok
parallel group (5 tests):  portals_p2 cluster rules select_views foreign_key
 select_views ... ok
 portals_p2   ... ok
 rules... ok
 foreign_key  ... ok
 cluster  ... ok
parallel group (11 tests):  limit truncate temp copy2 domain rangefuncs conversion 
prepare without_oid plpgsql alter_table
 limit... ok
 plpgsql  ... ok
 copy2... ok
 temp ... ok
 domain   ... ok
 rangefuncs   ... ok
 prepare  ... ok
 without_oid  ... ok
 conversion   ... ok
 truncate ... ok
 alter_table  ... ok


regression.diffs
-


*** ./expected/geometry-powerpc-aix4.outTue Sep 12 17:07:16 2000
--- ./results/geometry.out  Thu Nov 21 21:46:01 2002
***
*** 114,120 
  | (5.1,34.5) | [(1,2),(3,4)] | (3,4)
  | (-5,-12)   | [(1,2),(3,4)] | (1,2)
  | (10,10)| [(1,2),(3,4)] | (3,4)
! | (0,0)  | [(0,0),(6,6)] | (0,0)
  | (-10,0)| [(0,0),(6,6)] | (0,0)
  | (-3,4) | [(0,0),(6,6)] | (0.5,0.5)
  | (5.1,34.5) | [(0,0),(6,6)] | (6,6)
--- 114,120 
  | (5.1,34.5) | [(1,2),(3,4)] | (3,4)
  | (-5,-12)   | [(1,2),(3,4)] | (1,2)
  | (10,10)| [(1,2),(3,4)] | (3,4)
! | (0,0)  | [(0,0),(6,6)] | (-0,0)
  | (-10,0)| [(0,0),(6,6)]  

Re: [HACKERS] RC1?

[Bruce Momjian]

Ports list updated:

  http://candle.pha.pa.us/main/writings/pgsql/sgml/supported-platforms.html

---

Patrick Welche wrote:
> On Wed, Nov 20, 2002 at 09:33:41AM -0500, Bruce Momjian wrote:
> > Patrick Welche wrote:
> > > On Tue, Nov 19, 2002 at 06:22:08PM +0100, Peter Eisentraut wrote:
> > > > He was testing 7.4devel.  That's not the right one.
> > > 
> > > What's the difference? (Do I really want to wait another day while this
> > > ancient box compiles it given that the chances of it working under
> > > 7.4devel and not under 7.3rcN are smaller than the chances of it
> > > working under 7.3rcN and not under 7.4devel, no?)
> > 
> > Uh, you are right, but we have made a _few_ 7.4 changes so I do think we
> > need a 7.3-specific test.
> 
> OK - did 7.3rc1 successfully on NetBSD-1.6K/acorn32 and NetBSD-16H/i386
> 
> ---(end of broadcast)---
> TIP 5: Have you checked our extensive FAQ?
> 
> http://www.postgresql.org/users-lounge/docs/faq.html
> 

-- 
  Bruce Momjian|  http://candle.pha.pa.us
  [EMAIL PROTECTED]   |  (610) 359-1001
  +  If your life is a hard drive, |  13 Roberts Road
  +  Christ can be your backup.|  Newtown Square, Pennsylvania 19073

---(end of broadcast)---
TIP 6: Have you searched our list archives?

http://archives.postgresql.org

Re: [HACKERS] RC1?

[Patrick Welche]

On Wed, Nov 20, 2002 at 09:33:41AM -0500, Bruce Momjian wrote:
> Patrick Welche wrote:
> > On Tue, Nov 19, 2002 at 06:22:08PM +0100, Peter Eisentraut wrote:
> > > He was testing 7.4devel.  That's not the right one.
> > 
> > What's the difference? (Do I really want to wait another day while this
> > ancient box compiles it given that the chances of it working under
> > 7.4devel and not under 7.3rcN are smaller than the chances of it
> > working under 7.3rcN and not under 7.4devel, no?)
> 
> Uh, you are right, but we have made a _few_ 7.4 changes so I do think we
> need a 7.3-specific test.

And yes, you are right, I've just spotted a little change: 7.3b1 dump
imported into 7.4devel database needs "value" quoted in

CREATE TABLE amount (
id serial NOT NULL,
value integer
);

so "value"'s keyword status must have changed..

Cheers,

Patrick

---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly

Re: [HACKERS] RC1?

[Patrick Welche]

On Wed, Nov 20, 2002 at 09:33:41AM -0500, Bruce Momjian wrote:
> Patrick Welche wrote:
> > On Tue, Nov 19, 2002 at 06:22:08PM +0100, Peter Eisentraut wrote:
> > > He was testing 7.4devel.  That's not the right one.
> > 
> > What's the difference? (Do I really want to wait another day while this
> > ancient box compiles it given that the chances of it working under
> > 7.4devel and not under 7.3rcN are smaller than the chances of it
> > working under 7.3rcN and not under 7.4devel, no?)
> 
> Uh, you are right, but we have made a _few_ 7.4 changes so I do think we
> need a 7.3-specific test.

OK - did 7.3rc1 successfully on NetBSD-1.6K/acorn32 and NetBSD-16H/i386

---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/users-lounge/docs/faq.html

Re: [PORTS] Geometry test on NetBSD (was Re: [HACKERS] RC1?)

[Tom Lane]

Patrick Welche <[EMAIL PROTECTED]> writes:
>  Just realised: the answers I gave above were with the config.guess from
> automake 1.7a!

> % uname -srmp
> NetBSD 1.6K acorn32 arm
> % postgresql-7.3rc1/config/config.guess
> acorn32-unknown-netbsd1.6K
> % automake/lib/config.guess
> arm-unknown-netbsdelf1.6K

Mph.  Okay, I guess we'd better expend two patterns on this:

geometry/.*-netbsd1.[0-5]=geometry-positive-zeros
geometry/.*-netbsdelf1.[0-5]=geometry-positive-zeros

Will make it so.

regards, tom lane

---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster

Re: [PORTS] Geometry test on NetBSD (was Re: [HACKERS] RC1?)

[Patrick Welche]

On Wed, Nov 20, 2002 at 01:51:28PM -0500, Tom Lane wrote:
> Patrick Welche <[EMAIL PROTECTED]> writes:
> > On Wed, Nov 20, 2002 at 01:21:47PM -0500, Tom Lane wrote:
> >> Ah-hah, so it is a version issue --- we could make the resultmap line
> >> something like
> >> geometry/.*-netbsd1.[0-5]=geometry-positive-zeros
> 
> > NetBSD/i386-1.6H i386-unknown-netbsdelf1.6H (checked 7.3rc1)
> > NetBSD/acorn32-1.6K  arm-unknown-netbsdelf1.6K  (still building 7.3rc1)
> 
> Hm, is that "elf" always there?  I'm a little uncomfortable with making
> the pattern be
>   geometry/.*-netbsd.*1.[0-5]=geometry-positive-zeros
> as this seems way too lax ...

"elf" won't always be there - that acorn32 is a case in point: it became
elf for 1.6. acorn26 has always been elf. I can't remember when i386 became
elf.. (In fact the old config.guess that comes with NeTraMet44b8 says
i386-unknown-netbsd1.6K - so maybe the config.guess cvs log may shed some
light)


 Just realised: the answers I gave above were with the config.guess from
automake 1.7a!

% uname -srmp
NetBSD 1.6K acorn32 arm
% postgresql-7.3rc1/config/config.guess
acorn32-unknown-netbsd1.6K
% automake/lib/config.guess
arm-unknown-netbsdelf1.6K

Confusing..

Patrick

---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly

Re: [PORTS] Geometry test on NetBSD (was Re: [HACKERS] RC1?)

[Tom Lane]

Patrick Welche <[EMAIL PROTECTED]> writes:
> On Wed, Nov 20, 2002 at 01:21:47PM -0500, Tom Lane wrote:
>> Ah-hah, so it is a version issue --- we could make the resultmap line
>> something like
>> geometry/.*-netbsd1.[0-5]=geometry-positive-zeros

> NetBSD/i386-1.6H i386-unknown-netbsdelf1.6H (checked 7.3rc1)
> NetBSD/acorn32-1.6K  arm-unknown-netbsdelf1.6K  (still building 7.3rc1)

Hm, is that "elf" always there?  I'm a little uncomfortable with making
the pattern be
geometry/.*-netbsd.*1.[0-5]=geometry-positive-zeros
as this seems way too lax ...

regards, tom lane

---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/users-lounge/docs/faq.html

Re: [PORTS] Geometry test on NetBSD (was Re: [HACKERS] RC1?)

[Patrick Welche]

On Wed, Nov 20, 2002 at 01:21:47PM -0500, Tom Lane wrote:
> Patrick Welche <[EMAIL PROTECTED]> writes:
... 
> > NetBSD 1.5 has revision 1.32, NetBSD 1.6 has revision 1.42
> 
> Ah-hah, so it is a version issue --- we could make the resultmap line
> something like
>   geometry/.*-netbsd1.[0-5]=geometry-positive-zeros
> 
> Would you confirm what config.guess prints on your box --- in
> particular, is there a dot in the version number?

Yes:

NetBSD/i386-1.6H i386-unknown-netbsdelf1.6H (checked 7.3rc1)
NetBSD/acorn32-1.6K  arm-unknown-netbsdelf1.6K  (still building 7.3rc1)

(several NetBSDs probably come up with arm-unknown..)

Cheers,

Patrick

---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/users-lounge/docs/faq.html

Re: [PORTS] Geometry test on NetBSD (was Re: [HACKERS] RC1?)

[Tom Lane]

Peter Eisentraut <[EMAIL PROTECTED]> writes:
> The next FreeBSD subrelease (4.8?) should have this fixed.  OpenBSD is not
> fixed.  NetBSD and Darwin seem to have temporarily hidden their cvsweb in
> shame, but I would assume it's the same issue.  Not sure what HP-UX is
> doing about it.

HP has evidently fixed it in HPUX 11.  I do not think they intend to
change the behavior of HPUX 10 anymore, so the existing resultmap
entries for geometry/hppa seem okay.

regards, tom lane

---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster

Re: [PORTS] Geometry test on NetBSD (was Re: [HACKERS] RC1?)

[Tom Lane]

Patrick Welche <[EMAIL PROTECTED]> writes:
> Right, the equivalent for NetBSD vfprintf.c is:
> revision 1.40
> date: 2001/11/28 11:58:22;  author: kleink;  state: Exp;  lines: +4 -4
> Since we're returned the sign of a floating-point number by __dtoa(),
> use that to decide whether to include a minus sign in the result.
> Fixes printing -0.0, and thus PR lib/3137.

> NetBSD 1.5 has revision 1.32, NetBSD 1.6 has revision 1.42

Ah-hah, so it is a version issue --- we could make the resultmap line
something like
geometry/.*-netbsd1.[0-5]=geometry-positive-zeros

Would you confirm what config.guess prints on your box --- in
particular, is there a dot in the version number?

regards, tom lane

---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]

Re: [PORTS] Geometry test on NetBSD (was Re: [HACKERS] RC1?)

[Patrick Welche]

On Wed, Nov 20, 2002 at 06:48:15PM +0100, Peter Eisentraut wrote:
> Tom Lane writes:
> 
> > AFAIK, all modern hardware claims compliance to the IEEE floating-point
> > arithmetic standard, so failure to print minus zero as minus zero is
> > very likely to be a software issue not hardware.  That suggests strongly
> > that the issue is netbsd version (specifically libc version) and not the
> > hardware platform.
> 
> I could confirm my initial suspicion: it's a *printf() library issue.  The
> FreeBSD CVS log tells the tale:
> 
> http://www.de.freebsd.org/cgi/cvsweb.cgi/src/lib/libc/stdio/vfprintf.c
> 
> The next FreeBSD subrelease (4.8?) should have this fixed.  OpenBSD is not
> fixed.  NetBSD and Darwin seem to have temporarily hidden their cvsweb in
> shame, but I would assume it's the same issue.  Not sure what HP-UX is
> doing about it.

Right, the equivalent for NetBSD vfprintf.c is:

revision 1.40
date: 2001/11/28 11:58:22;  author: kleink;  state: Exp;  lines: +4 -4
Since we're returned the sign of a floating-point number by __dtoa(),
use that to decide whether to include a minus sign in the result.
Fixes printing -0.0, and thus PR lib/3137.

NetBSD 1.5 has revision 1.32, NetBSD 1.6 has revision 1.42

Well spotted,

Patrick

---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])

Re: [PORTS] Geometry test on NetBSD (was Re: [HACKERS] RC1?)

[Peter Eisentraut]

Tom Lane writes:

> AFAIK, all modern hardware claims compliance to the IEEE floating-point
> arithmetic standard, so failure to print minus zero as minus zero is
> very likely to be a software issue not hardware.  That suggests strongly
> that the issue is netbsd version (specifically libc version) and not the
> hardware platform.

I could confirm my initial suspicion: it's a *printf() library issue.  The
FreeBSD CVS log tells the tale:

http://www.de.freebsd.org/cgi/cvsweb.cgi/src/lib/libc/stdio/vfprintf.c

The next FreeBSD subrelease (4.8?) should have this fixed.  OpenBSD is not
fixed.  NetBSD and Darwin seem to have temporarily hidden their cvsweb in
shame, but I would assume it's the same issue.  Not sure what HP-UX is
doing about it.

-- 
Peter Eisentraut   [EMAIL PROTECTED]


---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster

Re: Geometry test on NetBSD (was Re: [HACKERS] RC1?)

[Ken Hirsch]

Bruce Momjian <[EMAIL PROTECTED]> wrote:
>
> Tom, can you clarify why -0 is valid.  Is it for _small_ near zero
> values that are indeed negative?
>

"Branch Cuts for Complex Elementary Functions,  or Much Ado About
Nothing's Sign Bit"  W. Kahan;  ch. 7 in _The State of the Art in
Numerical Analysis_ ed. by  M. Powell and A. Iserles 1987 Oxford.
Explains how proper respect for  -0  eases implementation of conformal
maps of slitted domains arising in studies of flows around obstacles.

Kahan was one of the most important people behind the floating point
standard and won the 1989 Turing Award for his work in numerical computing.
http://www.cs.berkeley.edu/~wkahan/ieee754status/754story.html

---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster

Re: [HACKERS] RC1?

[Bruce Momjian]

Patrick Welche wrote:
> On Tue, Nov 19, 2002 at 06:22:08PM +0100, Peter Eisentraut wrote:
> > He was testing 7.4devel.  That's not the right one.
> 
> What's the difference? (Do I really want to wait another day while this
> ancient box compiles it given that the chances of it working under
> 7.4devel and not under 7.3rcN are smaller than the chances of it
> working under 7.3rcN and not under 7.4devel, no?)

Uh, you are right, but we have made a _few_ 7.4 changes so I do think we
need a 7.3-specific test.

-- 
  Bruce Momjian|  http://candle.pha.pa.us
  [EMAIL PROTECTED]   |  (610) 359-1001
  +  If your life is a hard drive, |  13 Roberts Road
  +  Christ can be your backup.|  Newtown Square, Pennsylvania 19073

---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/users-lounge/docs/faq.html

Re: [HACKERS] RC1?

[Patrick Welche]

On Tue, Nov 19, 2002 at 06:22:08PM +0100, Peter Eisentraut wrote:
> He was testing 7.4devel.  That's not the right one.

What's the difference? (Do I really want to wait another day while this
ancient box compiles it given that the chances of it working under
7.4devel and not under 7.3rcN are smaller than the chances of it
working under 7.3rcN and not under 7.4devel, no?)

Patrick


---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]

Re: Geometry test on NetBSD (was Re: [HACKERS] RC1?)

[Tom Lane]

Bruce Momjian <[EMAIL PROTECTED]> writes:
> Tom, can you clarify why -0 is valid.

The IEEE spec absolutely thinks that -0 and +0 are distinct entities.
I don't remember why, at one in the morning ... but if you insist I'm
sure that plenty sufficient numerical-analysis reasons can be produced.
The guys who wrote that spec knew what they were doing (that's why it's
been adopted so universally).

regards, tom lane

---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])

Re: Geometry test on NetBSD (was Re: [HACKERS] RC1?)

[Bruce Momjian]

Tom, can you clarify why -0 is valid.  Is it for _small_ near zero
values that are indeed negative?

---

Tom Lane wrote:
> Patrick Welche <[EMAIL PROTECTED]> writes:
> > On Tue, Nov 19, 2002 at 10:53:59AM -0500, Tom Lane wrote:
> >> Presumably that was put in because it was correct on i86.  How do you
> >> feel about changing that entry to
> >> geometry/i.86-.*-netbsd=geometry-positive-zeros
> >> rather than deleting it?
> 
> > I was under the impression until now that it was geometry.out for i86 using
> > the libm387 math library, and geometry-positive-zeros for everyone else, but
> > this acorn32 box is also giving geometry.out, so I must be wrong, in fact
> > I've just tried not using libm387 on an i386, and it gives geometry.out
> > too, so we might as well delete it...
> 
> Hm.  Another possibility is that the existing resultmap entry is correct
> for some prior netbsd version, but is correct no longer.
> 
> AFAIK, all modern hardware claims compliance to the IEEE floating-point
> arithmetic standard, so failure to print minus zero as minus zero is
> very likely to be a software issue not hardware.  That suggests strongly
> that the issue is netbsd version (specifically libc version) and not the
> hardware platform.
> 
> If we knew which netbsd version the behavior changed at, we could put in
> some version-specific resultmap entries.  But unless someone can provide
> datapoints on that, I guess we'll just have to update resultmap to match
> recent versions --- ie, take out the entry pointing to
> geometry-positive-zeros.
> 
> Any objections out there?
> 
>   regards, tom lane
> 
> ---(end of broadcast)---
> TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
> 

-- 
  Bruce Momjian|  http://candle.pha.pa.us
  [EMAIL PROTECTED]   |  (610) 359-1001
  +  If your life is a hard drive, |  13 Roberts Road
  +  Christ can be your backup.|  Newtown Square, Pennsylvania 19073

---(end of broadcast)---
TIP 6: Have you searched our list archives?

http://archives.postgresql.org

Geometry test on NetBSD (was Re: [HACKERS] RC1?)

[Tom Lane]

Patrick Welche <[EMAIL PROTECTED]> writes:
> On Tue, Nov 19, 2002 at 10:53:59AM -0500, Tom Lane wrote:
>> Presumably that was put in because it was correct on i86.  How do you
>> feel about changing that entry to
>> geometry/i.86-.*-netbsd=geometry-positive-zeros
>> rather than deleting it?

> I was under the impression until now that it was geometry.out for i86 using
> the libm387 math library, and geometry-positive-zeros for everyone else, but
> this acorn32 box is also giving geometry.out, so I must be wrong, in fact
> I've just tried not using libm387 on an i386, and it gives geometry.out
> too, so we might as well delete it...

Hm.  Another possibility is that the existing resultmap entry is correct
for some prior netbsd version, but is correct no longer.

AFAIK, all modern hardware claims compliance to the IEEE floating-point
arithmetic standard, so failure to print minus zero as minus zero is
very likely to be a software issue not hardware.  That suggests strongly
that the issue is netbsd version (specifically libc version) and not the
hardware platform.

If we knew which netbsd version the behavior changed at, we could put in
some version-specific resultmap entries.  But unless someone can provide
datapoints on that, I guess we'll just have to update resultmap to match
recent versions --- ie, take out the entry pointing to
geometry-positive-zeros.

Any objections out there?

regards, tom lane

---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])

Re: [HACKERS] RC1?

[Bruce Momjian]

Backed out. Peter. thanks for spotting that.

Patrick, would you please test 7.3RC1?

---

Peter Eisentraut wrote:
> He was testing 7.4devel.  That's not the right one.
> 
> Bruce Momjian writes:
> 
> >
> > Ports list updated:
> >
> >   http://candle.pha.pa.us/main/writings/pgsql/sgml/supported-platforms.html
> >
> > ---
> > Patrick Welche wrote:
> > > On Thu, Nov 14, 2002 at 09:06:01AM -0500, Tom Lane wrote:
> > > > "Magnus Naeslund(f)" <[EMAIL PROTECTED]> writes:
> > > > > OK OK, before anyone rubs my nose in it, i see the fork() failures :)
> > > >
> > > > > I'll see what's causing the fork() problems...
> > > >
> > > > Too low processes-per-user limit, likely.
> > >
> > > Success for
> > >  PostgreSQL 7.4devel on acorn32-unknown-netbsd1.6K, compiled by GCC 2.95.3
> > >
> > > In other words NetBSD/acorn32-1.6K. The fork() problem for me was not
> > > enough memory, but checking with --schedule=./serial_schedule made it pass
> > > all the tests, except geometry, which leads me to change my mind and
> > > suggest:
> > >
> > > Index: resultmap
> > > ===
> > > RCS file: /projects/cvsroot/pgsql-server/src/test/regress/resultmap,v
> > > retrieving revision 1.59
> > > diff -u -r1.59 resultmap
> > > --- resultmap   2002/11/12 20:02:32 1.59
> > > +++ resultmap   2002/11/19 15:20:19
> > > @@ -18,7 +18,6 @@
> > >  geometry/alpha.*-freebsd4.[0-5]=geometry-positive-zeros
> > >  geometry/i.86-.*-openbsd=geometry-positive-zeros
> > >  geometry/sparc-.*-openbsd=geometry-positive-zeros
> > > -geometry/.*-netbsd=geometry-positive-zeros
> > >  geometry/hppa.*-hpux9=geometry-positive-zeros
> > >  geometry/hppa.*-hpux10=geometry-positive-zeros
> > >  geometry/.*-irix6=geometry-positive-zeros
> > >
> > >
> > > as this acorn32 is running on a StrongARM processor, so has nothing to do
> > > with libm387. Maybe get rid of the geometry-positive-zeros and see if
> > > someone complains and tells me otherwise?
> > >
> > > Cheers,
> > >
> > > Patrick
> > >
> > > ---(end of broadcast)---
> > > TIP 6: Have you searched our list archives?
> > >
> > > http://archives.postgresql.org
> > >
> >
> >
> 
> -- 
> Peter Eisentraut   [EMAIL PROTECTED]
> 
> 

-- 
  Bruce Momjian|  http://candle.pha.pa.us
  [EMAIL PROTECTED]   |  (610) 359-1001
  +  If your life is a hard drive, |  13 Roberts Road
  +  Christ can be your backup.|  Newtown Square, Pennsylvania 19073

---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]

Re: [HACKERS] RC1?

[Peter Eisentraut]

He was testing 7.4devel.  That's not the right one.

Bruce Momjian writes:

>
> Ports list updated:
>
>   http://candle.pha.pa.us/main/writings/pgsql/sgml/supported-platforms.html
>
> ---
> Patrick Welche wrote:
> > On Thu, Nov 14, 2002 at 09:06:01AM -0500, Tom Lane wrote:
> > > "Magnus Naeslund(f)" <[EMAIL PROTECTED]> writes:
> > > > OK OK, before anyone rubs my nose in it, i see the fork() failures :)
> > >
> > > > I'll see what's causing the fork() problems...
> > >
> > > Too low processes-per-user limit, likely.
> >
> > Success for
> >  PostgreSQL 7.4devel on acorn32-unknown-netbsd1.6K, compiled by GCC 2.95.3
> >
> > In other words NetBSD/acorn32-1.6K. The fork() problem for me was not
> > enough memory, but checking with --schedule=./serial_schedule made it pass
> > all the tests, except geometry, which leads me to change my mind and
> > suggest:
> >
> > Index: resultmap
> > ===
> > RCS file: /projects/cvsroot/pgsql-server/src/test/regress/resultmap,v
> > retrieving revision 1.59
> > diff -u -r1.59 resultmap
> > --- resultmap   2002/11/12 20:02:32 1.59
> > +++ resultmap   2002/11/19 15:20:19
> > @@ -18,7 +18,6 @@
> >  geometry/alpha.*-freebsd4.[0-5]=geometry-positive-zeros
> >  geometry/i.86-.*-openbsd=geometry-positive-zeros
> >  geometry/sparc-.*-openbsd=geometry-positive-zeros
> > -geometry/.*-netbsd=geometry-positive-zeros
> >  geometry/hppa.*-hpux9=geometry-positive-zeros
> >  geometry/hppa.*-hpux10=geometry-positive-zeros
> >  geometry/.*-irix6=geometry-positive-zeros
> >
> >
> > as this acorn32 is running on a StrongARM processor, so has nothing to do
> > with libm387. Maybe get rid of the geometry-positive-zeros and see if
> > someone complains and tells me otherwise?
> >
> > Cheers,
> >
> > Patrick
> >
> > ---(end of broadcast)---
> > TIP 6: Have you searched our list archives?
> >
> > http://archives.postgresql.org
> >
>
>

-- 
Peter Eisentraut   [EMAIL PROTECTED]


---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]

Re: [HACKERS] RC1?

[Patrick Welche]

On Tue, Nov 19, 2002 at 10:53:59AM -0500, Tom Lane wrote:
> Patrick Welche <[EMAIL PROTECTED]> writes:
> > [remove this:]
> > -geometry/.*-netbsd=geometry-positive-zeros
> 
> > as this acorn32 is running on a StrongARM processor, so has nothing to do
> > with libm387. Maybe get rid of the geometry-positive-zeros and see if
> > someone complains and tells me otherwise?
> 
> Presumably that was put in because it was correct on i86.  How do you
> feel about changing that entry to
> 
>   geometry/i.86-.*-netbsd=geometry-positive-zeros
> 
> rather than deleting it?

I was under the impression until now that it was geometry.out for i86 using
the libm387 math library, and geometry-positive-zeros for everyone else, but
this acorn32 box is also giving geometry.out, so I must be wrong, in fact
I've just tried not using libm387 on an i386, and it gives geometry.out
too, so we might as well delete it...

BTW cluster.out wants changing now that the ALL in CLUSTER ALL is no longer
allowed..

Cheers,

Patrick

---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster

Re: [HACKERS] RC1?

[Bruce Momjian]

Ports list updated:

  http://candle.pha.pa.us/main/writings/pgsql/sgml/supported-platforms.html

---
Patrick Welche wrote:
> On Thu, Nov 14, 2002 at 09:06:01AM -0500, Tom Lane wrote:
> > "Magnus Naeslund(f)" <[EMAIL PROTECTED]> writes:
> > > OK OK, before anyone rubs my nose in it, i see the fork() failures :)
> > 
> > > I'll see what's causing the fork() problems...
> > 
> > Too low processes-per-user limit, likely.
> 
> Success for
>  PostgreSQL 7.4devel on acorn32-unknown-netbsd1.6K, compiled by GCC 2.95.3
> 
> In other words NetBSD/acorn32-1.6K. The fork() problem for me was not
> enough memory, but checking with --schedule=./serial_schedule made it pass
> all the tests, except geometry, which leads me to change my mind and
> suggest:
> 
> Index: resultmap
> ===
> RCS file: /projects/cvsroot/pgsql-server/src/test/regress/resultmap,v
> retrieving revision 1.59
> diff -u -r1.59 resultmap
> --- resultmap   2002/11/12 20:02:32 1.59
> +++ resultmap   2002/11/19 15:20:19
> @@ -18,7 +18,6 @@
>  geometry/alpha.*-freebsd4.[0-5]=geometry-positive-zeros
>  geometry/i.86-.*-openbsd=geometry-positive-zeros
>  geometry/sparc-.*-openbsd=geometry-positive-zeros
> -geometry/.*-netbsd=geometry-positive-zeros
>  geometry/hppa.*-hpux9=geometry-positive-zeros
>  geometry/hppa.*-hpux10=geometry-positive-zeros
>  geometry/.*-irix6=geometry-positive-zeros
> 
> 
> as this acorn32 is running on a StrongARM processor, so has nothing to do
> with libm387. Maybe get rid of the geometry-positive-zeros and see if
> someone complains and tells me otherwise?
> 
> Cheers,
> 
> Patrick
> 
> ---(end of broadcast)---
> TIP 6: Have you searched our list archives?
> 
> http://archives.postgresql.org
> 

-- 
  Bruce Momjian|  http://candle.pha.pa.us
  [EMAIL PROTECTED]   |  (610) 359-1001
  +  If your life is a hard drive, |  13 Roberts Road
  +  Christ can be your backup.|  Newtown Square, Pennsylvania 19073

---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly

Re: [HACKERS] RC1?

[Tom Lane]

Patrick Welche <[EMAIL PROTECTED]> writes:
> [remove this:]
> -geometry/.*-netbsd=geometry-positive-zeros

> as this acorn32 is running on a StrongARM processor, so has nothing to do
> with libm387. Maybe get rid of the geometry-positive-zeros and see if
> someone complains and tells me otherwise?

Presumably that was put in because it was correct on i86.  How do you
feel about changing that entry to

geometry/i.86-.*-netbsd=geometry-positive-zeros

rather than deleting it?

regards, tom lane

---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/users-lounge/docs/faq.html

Re: [HACKERS] RC1?

[Patrick Welche]

On Thu, Nov 14, 2002 at 09:06:01AM -0500, Tom Lane wrote:
> "Magnus Naeslund(f)" <[EMAIL PROTECTED]> writes:
> > OK OK, before anyone rubs my nose in it, i see the fork() failures :)
> 
> > I'll see what's causing the fork() problems...
> 
> Too low processes-per-user limit, likely.

Success for
 PostgreSQL 7.4devel on acorn32-unknown-netbsd1.6K, compiled by GCC 2.95.3

In other words NetBSD/acorn32-1.6K. The fork() problem for me was not
enough memory, but checking with --schedule=./serial_schedule made it pass
all the tests, except geometry, which leads me to change my mind and
suggest:

Index: resultmap
===
RCS file: /projects/cvsroot/pgsql-server/src/test/regress/resultmap,v
retrieving revision 1.59
diff -u -r1.59 resultmap
--- resultmap   2002/11/12 20:02:32 1.59
+++ resultmap   2002/11/19 15:20:19
@@ -18,7 +18,6 @@
 geometry/alpha.*-freebsd4.[0-5]=geometry-positive-zeros
 geometry/i.86-.*-openbsd=geometry-positive-zeros
 geometry/sparc-.*-openbsd=geometry-positive-zeros
-geometry/.*-netbsd=geometry-positive-zeros
 geometry/hppa.*-hpux9=geometry-positive-zeros
 geometry/hppa.*-hpux10=geometry-positive-zeros
 geometry/.*-irix6=geometry-positive-zeros


as this acorn32 is running on a StrongARM processor, so has nothing to do
with libm387. Maybe get rid of the geometry-positive-zeros and see if
someone complains and tells me otherwise?

Cheers,

Patrick

---(end of broadcast)---
TIP 6: Have you searched our list archives?

http://archives.postgresql.org

Re: [HACKERS] RC1?

[Matthew T. O'Connor]

> Tom, would you really be able to ask Permaine to retest 7.3?  Have a
> feeling we might be able to leverage the PlayStation2 brand name here
> for the Advocacy project.
>
> :-)
>

Anyone try it on an Xbox yet?

---(end of broadcast)---
TIP 6: Have you searched our list archives?

http://archives.postgresql.org

Re: [HACKERS] RC1?

[Scott Lamb]

Tom Lane wrote:


Seriously, I agree with Marc's opinion that issuing an RC1 is the best
way to flush out some more port reports.  I do not know what else we can
do to get people off their duffs and onto last-minute testing.


If testing is the problem, I think publicizing the betas would help 
more. I had no idea that 7.3b[2-5] had been released. And looking at the 
website, it's not hard to see why:

: No mention
 (or whatever mirror): No mention
: No mention
: Mentions beta has begun
: Shows latest release at 
bottom of page.

I'd really expect to see an announcement on the news page for each beta 
release and the latest stable/beta release on the front page. That would 
help more than releasing RC1, especially if it's done in the same way.

Thanks,
Scott


---(end of broadcast)---
TIP 6: Have you searched our list archives?

http://archives.postgresql.org

Re: [HACKERS] RC1?

[Patrick Welche]

On Thu, Nov 14, 2002 at 06:13:56PM +, Patrick Welche wrote:
> On Wed, Nov 13, 2002 at 07:53:00PM +0100, Peter Eisentraut wrote:
> > Tom Lane writes:
> > 
> > > We can't just wait around indefinitely for port reports that may or may
> > > not ever appear.  In any case, most of the "<7.3" entries in the list
> > > seem to be various flavors of *BSD; I think it's unlikely we broke
> > > those ...
> > 
> > Note that we have *zero* reports for any flavor of NetBSD and OpenBSD.
> > That is highly suspicious, and I would not venture a guess about how
> > likely it is they're broken.


PostgreSQL 7.3b1 on i386-unknown-netbsdelf1.6H, compiled by GCC 2.95.3
PostgreSQL 7.4devel on i386-unknown-netbsdelf1.6K, compiled by GCC 2.95.3

I in fact get geometry.out rather than geometry-positive-zeros.out, but I
think you get the former when you use libm387.so.0 instead of libm.so.0
which isn't exactly the general case for NetBSD, though I have only one
NetBSD/i386 box which can't make use of libm387 (it's a 486SX25)

The 7.4devel was with source from Nov 9 12:27 GMT, so I think rather close
to 7.3, and again with source from just now.

Cheers,

Patrick

---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster

Re: [HACKERS] RC1?

[Bruce Momjian]

Ports list updated:

  http://candle.pha.pa.us/main/writings/pgsql/sgml/supported-platforms.html

---
Patrick Welche wrote:
> On Wed, Nov 13, 2002 at 07:53:00PM +0100, Peter Eisentraut wrote:
> > Tom Lane writes:
> > 
> > > We can't just wait around indefinitely for port reports that may or may
> > > not ever appear.  In any case, most of the "<7.3" entries in the list
> > > seem to be various flavors of *BSD; I think it's unlikely we broke
> > > those ...
> > 
> > Note that we have *zero* reports for any flavor of NetBSD and OpenBSD.
> > That is highly suspicious, and I would not venture a guess about how
> > likely it is they're broken.
> 
> Does all OK on this count?
> 
>  PostgreSQL 7.3b1 on i386-unknown-netbsdelf1.6H, compiled by GCC 2.95.3
> 
> (I'm trying to build bison at the mo to have a go with whatever is in cvs
> tip at the moment.)
> 
> Cheers,
> 
> Patrick
> 

-- 
  Bruce Momjian|  http://candle.pha.pa.us
  [EMAIL PROTECTED]   |  (610) 359-1001
  +  If your life is a hard drive, |  13 Roberts Road
  +  Christ can be your backup.|  Newtown Square, Pennsylvania 19073

---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]

Re: [HACKERS] RC1?

[Patrick Welche]

On Wed, Nov 13, 2002 at 07:53:00PM +0100, Peter Eisentraut wrote:
> Tom Lane writes:
> 
> > We can't just wait around indefinitely for port reports that may or may
> > not ever appear.  In any case, most of the "<7.3" entries in the list
> > seem to be various flavors of *BSD; I think it's unlikely we broke
> > those ...
> 
> Note that we have *zero* reports for any flavor of NetBSD and OpenBSD.
> That is highly suspicious, and I would not venture a guess about how
> likely it is they're broken.

Does all OK on this count?

 PostgreSQL 7.3b1 on i386-unknown-netbsdelf1.6H, compiled by GCC 2.95.3

(I'm trying to build bison at the mo to have a go with whatever is in cvs
tip at the moment.)

Cheers,

Patrick

---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]

Re: [HACKERS] RC1?

[Tom Lane]

"Magnus Naeslund(f)" <[EMAIL PROTECTED]> writes:
> OK OK, before anyone rubs my nose in it, i see the fork() failures :)

> I'll see what's causing the fork() problems...

Too low processes-per-user limit, likely.

regards, tom lane

---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly

Re: [HACKERS] RC1?

[Magnus Naeslund(f)]

Magnus Naeslund(f) <[EMAIL PROTECTED]> wrote:
>
> Well, OpenBSD isn't dead :)
> But i have problems compiling 7.3b5 on it (OpenBSD 3.1 i386).
> I figured i should give it a go, since nobody else did, but i get many
> regression failures.
>

OK OK, before anyone rubs my nose in it, i see the fork() failures :)
I just sent the mail without looking.

I'll see what's causing the fork() problems...

Magnus


---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster

Re: [HACKERS] RC1?

[Magnus Naeslund(f)]

Tom Lane <[EMAIL PROTECTED]> wrote:
[snip]
>
>> Note that we have *zero* reports for any flavor of NetBSD and
>> OpenBSD.
>
> Maybe they're both dead platforms?  ;-)
>

Well, OpenBSD isn't dead :)
But i have problems compiling 7.3b5 on it (OpenBSD 3.1 i386).
I figured i should give it a go, since nobody else did, but i get many
regression failures.

Then i tried 7.2.3, and it too gives alot of regression failures.

Both were configured with:

./configure \
  --with-perl\
  --with-openssl \
  --enable-odbc  \
  --with-CXX

And nothing else.

The regression diffs can be found at:
http://gimme.smisk.nu/~mag/pgsql/


Is there some kind of gotcha with compiling pgsql on OpenBSD?
I've never tried it before.


Magnus


---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster

Re: [HACKERS] RC1?

[Justin Clift]

Tom Lane wrote:

> Anyone care about the PlayStation 2 port ;=) ?  I can get Permaine to
> retest if so.  Slightly more seriously, we did see a recent report of
> trouble on S/390 Linux, but the complainant didn't follow up...

Heh Heh Heh

Tom, would you really be able to ask Permaine to retest 7.3?  Have a
feeling we might be able to leverage the PlayStation2 brand name here
for the Advocacy project.

:-)

Regards and best wishes,

Justin Clift
 
> regards, tom lane


-- 
"My grandfather once told me that there are two kinds of people: those
who work and those who take the credit. He told me to try to be in the
first group; there was less competition there."
   - Indira Gandhi

---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/users-lounge/docs/faq.html

Re: [HACKERS] RC1?

[Bruce Momjian]

Neil Conway wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Tom Lane wrote:
> > > Anyone care about the PlayStation 2 port ;=) ?  I can get Permaine to
> > > retest if so.  Slightly more seriously, we did see a recent report of
> > > trouble on S/390 Linux, but the complainant didn't follow up...
> > 
> > I put an S/390 patch into current CVS --- too risky for 7.3 because it
> > played with the Power PC ASM instructions. I think we can assume that
> > port will not work for 7.3.
> 
> Erm, why? The S/390 patch you applied was just a performance
> optimization, AFAIK. I tried to track down the problem that the user
> reported with S/390, but it appeared that the machine in question had
> some serious hardware/software problems, so I gave up.

Oh, I was not sure.  I thought it had to do with compile and .asm tags,
and I felt it was too late to take such risks if it could effect larger
working platforms.  Were they using non-ASM for S/390 before the patch? 
I don't remember.

I guess there was another person who had hardware trouble.

-- 
  Bruce Momjian|  http://candle.pha.pa.us
  [EMAIL PROTECTED]   |  (610) 359-1001
  +  If your life is a hard drive, |  13 Roberts Road
  +  Christ can be your backup.|  Newtown Square, Pennsylvania 19073

---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster

Re: [HACKERS] RC1?

[Neil Conway]

Bruce Momjian <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
> > Anyone care about the PlayStation 2 port ;=) ?  I can get Permaine to
> > retest if so.  Slightly more seriously, we did see a recent report of
> > trouble on S/390 Linux, but the complainant didn't follow up...
> 
> I put an S/390 patch into current CVS --- too risky for 7.3 because it
> played with the Power PC ASM instructions. I think we can assume that
> port will not work for 7.3.

Erm, why? The S/390 patch you applied was just a performance
optimization, AFAIK. I tried to track down the problem that the user
reported with S/390, but it appeared that the machine in question had
some serious hardware/software problems, so I gave up.

Cheers,

Neil

-- 
Neil Conway <[EMAIL PROTECTED]> || PGP Key ID: DB3C29FC


---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]

Re: [HACKERS] RC1?

[Tom Lane]

"Christopher Kings-Lynne" <[EMAIL PROTECTED]> writes:
>> How shall we distinguish your version of freebsd from the ones that
>> need the other comparison file?

> He is using the FreeBSD 3.x series (which is quite old now), whereas most
> people are probably using 4.x.  I have no problems with regression tests on
> 4.x so perhaps it's something that changed??

How do you feel about resultmap entries

float8/i.86-.*-freebsd3=float8-fp-exception
float8/i.86-.*-freebsd4=float8-small-is-zero

to replace the existing

float8/i.86-.*-freebsd=float8-small-is-zero

Are there (now or in the foreseeable future) freebsd major versions > 4?
We could do

float8/i.86-.*-freebsd[4-9]=float8-small-is-zero

which might or might not be more future-proof.

> Actually, I've only tested FreeBSD/alpha 4.x - perhaps I should test intel
> as well.

  ain't none of the float8 bsd resultmap entries will match alpha...
so you must be matching the default version?

regards, tom lane

---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/users-lounge/docs/faq.html

Re: [HACKERS] RC1?

[Bruce Momjian]

Christopher Kings-Lynne wrote:
> > > We can't just wait around indefinitely for port reports that may or may
> > > not ever appear.  In any case, most of the "<7.3" entries in the list
> > > seem to be various flavors of *BSD; I think it's unlikely we broke
> > > those ...
> >
> > Note that we have *zero* reports for any flavor of NetBSD and OpenBSD.
> > That is highly suspicious, and I would not venture a guess about how
> > likely it is they're broken.
> 
> Where is the list of supported platforms and the email addresses of those
> who sent in reports in earlier times?  I will email them to do testing...

List is at:

http://candle.pha.pa.us/main/writings/pgsql/sgml/supported-platforms.html

-- 
  Bruce Momjian|  http://candle.pha.pa.us
  [EMAIL PROTECTED]   |  (610) 359-1001
  +  If your life is a hard drive, |  13 Roberts Road
  +  Christ can be your backup.|  Newtown Square, Pennsylvania 19073

---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/users-lounge/docs/faq.html

Re: [HACKERS] RC1?

[Bruce Momjian]

I added it to the ports list as OK.  We can deal with fixing the
regression falure independently.


---

Nigel J. Andrews wrote:
> On Wed, 13 Nov 2002, Tom Lane wrote:
> 
> > "Nigel J. Andrews" <[EMAIL PROTECTED]> writes:
> > > FWIW, gmake check and gmake bigcheck pass on:
> > > FreeBSD 3.3-RELEASE #3: Thu Feb  3 23:48:56 GMT 2000
> > 
> > > with the expection of:
> > > [snipped]
> > > in the float8 test.
> > 
> > Okay, looks like we need to use float8-fp-exception.out on your
> > platform.  This is a bit surprising since resultmap presently shows
> > 
> > float8/i.86-.*-freebsd=float8-small-is-zero
> > 
> > How shall we distinguish your version of freebsd from the ones that
> > need the other comparison file?
> > 
> > regards, tom lane
> > 
> 
> Is it necessary, I mean really necessary to distinguish this system? It's quite
> an old installation [that ain't broke so I ain't fixed it] and the difference
> is only the error message. I hadn't even looked to see if there was a better
> expected output file, just accepted it as a normal, acceptable variation in
> the regression tests.
> 
> I don't know anything about how the tests are put together so I'd have to look
> into that before suggesting a way to differentiate my system. Having said that
> wouldn't the 3.3-RELEASE string be sufficient?
> 
> 
> 
> -- 
> Nigel J. Andrews
> 
> 
> ---(end of broadcast)---
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to [EMAIL PROTECTED] so that your
> message can get through to the mailing list cleanly
> 

-- 
  Bruce Momjian|  http://candle.pha.pa.us
  [EMAIL PROTECTED]   |  (610) 359-1001
  +  If your life is a hard drive, |  13 Roberts Road
  +  Christ can be your backup.|  Newtown Square, Pennsylvania 19073

---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]

Re: [HACKERS] RC1?

[Bruce Momjian]

Tom Lane wrote:
> Peter Eisentraut <[EMAIL PROTECTED]> writes:
> > Tom Lane writes:
> >> We can't just wait around indefinitely for port reports that may or may
> >> not ever appear.  In any case, most of the "<7.3" entries in the list
> >> seem to be various flavors of *BSD; I think it's unlikely we broke
> >> those ...
> 
> > Note that we have *zero* reports for any flavor of NetBSD and OpenBSD.
> 
> Maybe they're both dead platforms?  ;-)
> 
> Seriously, I agree with Marc's opinion that issuing an RC1 is the best
> way to flush out some more port reports.  I do not know what else we can
> do to get people off their duffs and onto last-minute testing.
> 
> > (Maybe you could get someone from Red Hat to confirm the remaining Linux
> > ports?)
> 
> Anyone care about the PlayStation 2 port ;=) ?  I can get Permaine to
> retest if so.  Slightly more seriously, we did see a recent report of
> trouble on S/390 Linux, but the complainant didn't follow up...

I put an S/390 patch into current CVS --- too risky for 7.3 because it
played with the Power PC ASM instructions. I think we can assume that
port will not work for 7.3.

-- 
  Bruce Momjian|  http://candle.pha.pa.us
  [EMAIL PROTECTED]   |  (610) 359-1001
  +  If your life is a hard drive, |  13 Roberts Road
  +  Christ can be your backup.|  Newtown Square, Pennsylvania 19073

---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]

Re: [HACKERS] RC1?

[Tom Lane]

Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Tom Lane writes:
>> We can't just wait around indefinitely for port reports that may or may
>> not ever appear.  In any case, most of the "<7.3" entries in the list
>> seem to be various flavors of *BSD; I think it's unlikely we broke
>> those ...

> Note that we have *zero* reports for any flavor of NetBSD and OpenBSD.

Maybe they're both dead platforms?  ;-)

Seriously, I agree with Marc's opinion that issuing an RC1 is the best
way to flush out some more port reports.  I do not know what else we can
do to get people off their duffs and onto last-minute testing.

> (Maybe you could get someone from Red Hat to confirm the remaining Linux
> ports?)

Anyone care about the PlayStation 2 port ;=) ?  I can get Permaine to
retest if so.  Slightly more seriously, we did see a recent report of
trouble on S/390 Linux, but the complainant didn't follow up...

regards, tom lane

---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster

Re: [HACKERS] RC1?

[Bruce Momjian]

Ports list updated:

  http://candle.pha.pa.us/main/writings/pgsql/sgml/supported-platforms.html

---
 Nigel J. Andrews wrote:
> On Tue, 12 Nov 2002, Tom Lane wrote:
> 
> > Peter Eisentraut <[EMAIL PROTECTED]> writes:
> > > Bruce Momjian writes:
> > >> Are we ready for RC1 yet?
> > 
> > > Questionable.  We don't even have 50% confirmation coverage for the
> > > supported platforms yet.
> > 
> > We can't just wait around indefinitely for port reports that may or may
> > not ever appear.  In any case, most of the "<7.3" entries in the list
> > seem to be various flavors of *BSD; I think it's unlikely we broke
> > those ...
> > 
> 
> 
> FWIW, gmake check and gmake bigcheck pass on:
> 
> FreeBSD 3.3-RELEASE #3: Thu Feb  3 23:48:56 GMT 2000
> 
> using:
> 
> gcc -v
> gcc version 2.7.2.3
> 
> and
> 
> ld -v
> GNU ld version 2.9.1 (with BFD 2.9.1)
> 
> with:
> 
> ./configure  --prefix=/usr/local/pgsql-7.2.1 --enable-multibyte --with-perl 
>--with-tcl --enable-odbc --with-pam --enable-syslog 
>--with-tclconfig=/usr/local/lib/tcl8.0 --with-tkconfig=/usr/local/lib/tk8.0 
>--with-includes=/usr/local/include/tcl8.0:/usr/local/include/tk8.0
> 
> with the expection of:
> 
> *** 214,220 
>  SET f1 = FLOAT8_TBL.f1 * '-1'
>  WHERE FLOAT8_TBL.f1 > '0.0';
>   SELECT '' AS bad, f.f1 * '1e200' from FLOAT8_TBL f;
> ! ERROR:  Bad float8 input format -- overflow
>   SELECT '' AS bad, f.f1 ^ '1e200' from FLOAT8_TBL f;
>   ERROR:  pow() result is out of range
>   SELECT '' AS bad, ln(f.f1) from FLOAT8_TBL f where f.f1 = '0.0' ;
> --- 214,220 
>  SET f1 = FLOAT8_TBL.f1 * '-1'
>  WHERE FLOAT8_TBL.f1 > '0.0';
>   SELECT '' AS bad, f.f1 * '1e200' from FLOAT8_TBL f;
> ! ERROR:  floating point exception! The last floating point operation either 
>exceeded legal ranges
>  or was a divide by zero
>   SELECT '' AS bad, f.f1 ^ '1e200' from FLOAT8_TBL f;
>   ERROR:  pow() result is out of range
>   SELECT '' AS bad, ln(f.f1) from FLOAT8_TBL f where f.f1 = '0.0' ;
> 
> in the float8 test.
> 
> 
> -- 
> Nigel J. Andrews
> Logictree Systems Limited
> 
> 
> 
> 
> ---(end of broadcast)---
> TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
> 

-- 
  Bruce Momjian|  http://candle.pha.pa.us
  [EMAIL PROTECTED]   |  (610) 359-1001
  +  If your life is a hard drive, |  13 Roberts Road
  +  Christ can be your backup.|  Newtown Square, Pennsylvania 19073

---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly

Re: [HACKERS] RC1?

[Christopher Kings-Lynne]

> "Nigel J. Andrews" <[EMAIL PROTECTED]> writes:
> > FWIW, gmake check and gmake bigcheck pass on:
> > FreeBSD 3.3-RELEASE #3: Thu Feb  3 23:48:56 GMT 2000
>
> > with the expection of:
> > [snipped]
> > in the float8 test.
>
> Okay, looks like we need to use float8-fp-exception.out on your
> platform.  This is a bit surprising since resultmap presently shows
>
>   float8/i.86-.*-freebsd=float8-small-is-zero
>
> How shall we distinguish your version of freebsd from the ones that
> need the other comparison file?

He is using the FreeBSD 3.x series (which is quite old now), whereas most
people are probably using 4.x.  I have no problems with regression tests on
4.x so perhaps it's something that changed??

Actually, I've only tested FreeBSD/alpha 4.x - perhaps I should test intel
as well.

Chris


---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly

Re: [HACKERS] RC1?

[Christopher Kings-Lynne]

> > We can't just wait around indefinitely for port reports that may or may
> > not ever appear.  In any case, most of the "<7.3" entries in the list
> > seem to be various flavors of *BSD; I think it's unlikely we broke
> > those ...
>
> Note that we have *zero* reports for any flavor of NetBSD and OpenBSD.
> That is highly suspicious, and I would not venture a guess about how
> likely it is they're broken.

Where is the list of supported platforms and the email addresses of those
who sent in reports in earlier times?  I will email them to do testing...

Chris


---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly

Re: [HACKERS] RC1?

[Tom Lane]

"Nigel J. Andrews" <[EMAIL PROTECTED]> writes:
> I don't know anything about how the tests are put together so I'd have
> to look into that before suggesting a way to differentiate my
> system. Having said that wouldn't the 3.3-RELEASE string be
> sufficient?

The mechanism we have in place relies on looking at the output of
config.guess (read the Admin Guide's info about the regression test
resultmap).  What does config.guess print for you?

regards, tom lane

---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster

Re: [HACKERS] RC1?

[Nigel J. Andrews]

On Wed, 13 Nov 2002, Tom Lane wrote:

> "Nigel J. Andrews" <[EMAIL PROTECTED]> writes:
> > FWIW, gmake check and gmake bigcheck pass on:
> > FreeBSD 3.3-RELEASE #3: Thu Feb  3 23:48:56 GMT 2000
> 
> > with the expection of:
> > [snipped]
> > in the float8 test.
> 
> Okay, looks like we need to use float8-fp-exception.out on your
> platform.  This is a bit surprising since resultmap presently shows
> 
>   float8/i.86-.*-freebsd=float8-small-is-zero
> 
> How shall we distinguish your version of freebsd from the ones that
> need the other comparison file?
> 
>   regards, tom lane
> 

Is it necessary, I mean really necessary to distinguish this system? It's quite
an old installation [that ain't broke so I ain't fixed it] and the difference
is only the error message. I hadn't even looked to see if there was a better
expected output file, just accepted it as a normal, acceptable variation in
the regression tests.

I don't know anything about how the tests are put together so I'd have to look
into that before suggesting a way to differentiate my system. Having said that
wouldn't the 3.3-RELEASE string be sufficient?



-- 
Nigel J. Andrews


---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly

Re: [HACKERS] RC1?

[Tom Lane]

"Nigel J. Andrews" <[EMAIL PROTECTED]> writes:
> FWIW, gmake check and gmake bigcheck pass on:
> FreeBSD 3.3-RELEASE #3: Thu Feb  3 23:48:56 GMT 2000

> with the expection of:
> [snipped]
> in the float8 test.

Okay, looks like we need to use float8-fp-exception.out on your
platform.  This is a bit surprising since resultmap presently shows

float8/i.86-.*-freebsd=float8-small-is-zero

How shall we distinguish your version of freebsd from the ones that
need the other comparison file?

regards, tom lane

---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])

Re: [HACKERS] RC1?

[scott.marlowe]

On Tue, 12 Nov 2002, Tom Lane wrote:

> "scott.marlowe" <[EMAIL PROTECTED]> writes:
> > Ok, now that I've run it that way, the last couple of pages of output 
> > look like this:
> 
> Hm.  So the "while read line" loop is iterating only once.
> 
> I was thinking to myself that something within the while loop must be
> eating up stdin, so that there's nothing left for the "while read" to
> read when control returns to the top of the loop.  This strengthens that
> theory.  Now, exactly what is reading stdin?
> 
> My suspicion falls on the very-recently-added awk calls.  Try changing
> 
> (echo "SET autocommit TO 'on';"; awk 'BEGIN {printf "\\set ECHO all\n"}'; 
>cat "$inputdir/sql/$1.sql") |
> 
> to
> 
> (echo "SET autocommit TO 'on';"; awk 'BEGIN {printf "\\set ECHO all\n"}' 
> 
> (there are two places to do this)

OK, that gets it to run all tests, but now virtually all of them fail...




---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])

Re: [HACKERS] RC1?

[cbbrowne]

On Wed, 13 Nov 2002 10:06:15 EST, the world broke into rejoicing as
Tom Lane <[EMAIL PROTECTED]>  said:
> "Zeugswetter Andreas SB SD" <[EMAIL PROTECTED]> writes:
> > Why use awk for this at all ? and not:
> > echo "\\set ECHO all"
> 
> I think Bruce is worried about portability; some versions of echo might
> do something weird with the backslash.  OTOH, it's not obvious to me
> that awk is better on that score.  Bruce?

The problem is that the regress script isn't pointing to the version of
awk that was picked up in the autoconf phase.

(More detailed comments forwarded directly :-).)

The "real deal" on what happens on Solaris is thus, from the awk FAQ,
where Patrick McPhee writes:

> SunOS includes three versions of awk. /usr/bin/awk is the old
> (pre-1989) version. /usr/bin/nawk is the new awk which appeared in
> 1989, and /usr/xpg4/bin/awk is supposed to conform to the single unix
> specification.  No one knows why Sun continues to ship old awk.

I would be /very/ inclined to trust Patrick's wisdom on this.

So long as we fix up the regression script to grab the "nawk" that
we expect to work, that's probably nicer than figuring out which
echo parameters are needed...
--
(concatenate 'string "cbbrowne" "@ntlug.org")
http://cbbrowne.com/info/wp.html
The first cup of coffee recapitulates phylogeny.

---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/users-lounge/docs/faq.html

Re: [HACKERS] RC1?

[Tom Lane]

> "Zeugswetter Andreas SB SD" <[EMAIL PROTECTED]> writes:
>> Why use awk for this at all ? and not:
>> echo "\\set ECHO all"

Actually, some googling revealed the following advice (in the Autoconf
manual):

 Because of these problems, do not pass a string containing
 arbitrary characters to echo. For example, echo "$foo" is safe if
 you know that foo's value cannot contain backslashes and cannot
 start with -, but otherwise you should use a here-document like
 this:

 cat <

Re: [HACKERS] RC1?

[Tom Lane]

"Zeugswetter Andreas SB SD" <[EMAIL PROTECTED]> writes:
> Why use awk for this at all ? and not:
> echo "\\set ECHO all"

I think Bruce is worried about portability; some versions of echo might
do something weird with the backslash.  OTOH, it's not obvious to me
that awk is better on that score.  Bruce?

regards, tom lane

---(end of broadcast)---
TIP 6: Have you searched our list archives?

http://archives.postgresql.org

Re: [HACKERS] RC1?

[Zeugswetter Andreas SB SD]

> My suspicion falls on the very-recently-added awk calls.  Try changing
> 
> (echo "SET autocommit TO 'on';"; awk 'BEGIN {printf 
> "\\set ECHO all\n"}'; cat "$inputdir/sql/$1.sql") |

Why use awk for this at all ? and not:
echo "\\set ECHO all"

??
Andreas

---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]

Re: [HACKERS] RC1?

[Nigel J. Andrews]

On Tue, 12 Nov 2002, Tom Lane wrote:

> Peter Eisentraut <[EMAIL PROTECTED]> writes:
> > Bruce Momjian writes:
> >> Are we ready for RC1 yet?
> 
> > Questionable.  We don't even have 50% confirmation coverage for the
> > supported platforms yet.
> 
> We can't just wait around indefinitely for port reports that may or may
> not ever appear.  In any case, most of the "<7.3" entries in the list
> seem to be various flavors of *BSD; I think it's unlikely we broke
> those ...
> 


FWIW, gmake check and gmake bigcheck pass on:

FreeBSD 3.3-RELEASE #3: Thu Feb  3 23:48:56 GMT 2000

using:

gcc -v
gcc version 2.7.2.3

and

ld -v
GNU ld version 2.9.1 (with BFD 2.9.1)

with:

./configure  --prefix=/usr/local/pgsql-7.2.1 --enable-multibyte --with-perl --with-tcl 
--enable-odbc --with-pam --enable-syslog --with-tclconfig=/usr/local/lib/tcl8.0 
--with-tkconfig=/usr/local/lib/tk8.0 
--with-includes=/usr/local/include/tcl8.0:/usr/local/include/tk8.0

with the expection of:

*** 214,220 
 SET f1 = FLOAT8_TBL.f1 * '-1'
 WHERE FLOAT8_TBL.f1 > '0.0';
  SELECT '' AS bad, f.f1 * '1e200' from FLOAT8_TBL f;
! ERROR:  Bad float8 input format -- overflow
  SELECT '' AS bad, f.f1 ^ '1e200' from FLOAT8_TBL f;
  ERROR:  pow() result is out of range
  SELECT '' AS bad, ln(f.f1) from FLOAT8_TBL f where f.f1 = '0.0' ;
--- 214,220 
 SET f1 = FLOAT8_TBL.f1 * '-1'
 WHERE FLOAT8_TBL.f1 > '0.0';
  SELECT '' AS bad, f.f1 * '1e200' from FLOAT8_TBL f;
! ERROR:  floating point exception! The last floating point operation either exceeded 
legal ranges
 or was a divide by zero
  SELECT '' AS bad, f.f1 ^ '1e200' from FLOAT8_TBL f;
  ERROR:  pow() result is out of range
  SELECT '' AS bad, ln(f.f1) from FLOAT8_TBL f where f.f1 = '0.0' ;

in the float8 test.


-- 
Nigel J. Andrews
Logictree Systems Limited




---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]

Re: [HACKERS] RC1?

[Tom Lane]

"scott.marlowe" <[EMAIL PROTECTED]> writes:
> Ok, now that I've run it that way, the last couple of pages of output 
> look like this:

Hm.  So the "while read line" loop is iterating only once.

I was thinking to myself that something within the while loop must be
eating up stdin, so that there's nothing left for the "while read" to
read when control returns to the top of the loop.  This strengthens that
theory.  Now, exactly what is reading stdin?

My suspicion falls on the very-recently-added awk calls.  Try changing

(echo "SET autocommit TO 'on';"; awk 'BEGIN {printf "\\set ECHO all\n"}'; cat 
"$inputdir/sql/$1.sql") |

to

(echo "SET autocommit TO 'on';"; awk 'BEGIN {printf "\\set ECHO all\n"}' 
http://www.postgresql.org/users-lounge/docs/faq.html

Re: [HACKERS] RC1?

[scott.marlowe]

On Tue, 12 Nov 2002, Tom Lane wrote:

> "scott.marlowe" <[EMAIL PROTECTED]> writes:
> > OK, make -x check fails, is there some other way to use -x I'm not 
> > thinking of here?
> 
> I was thinking of running the script by hand, not via make:
> 
> /bin/sh -x ./pg_regress --temp-install --top-builddir=../../.. 
>--schedule=./parallel_schedule --multibyte=SQL_ASCII

Ok, now that I've run it that way, the last couple of pages of output 
look like this:

formatted=numeric
+ echo  numeric  ... \c
EXPECTED=./expected/numeric
 numeric  ... + expr abstime=abstime-solaris-1947 : 
numeric=
+ [ 0 -ne 0 ]
+ expr geometry=geometry-solaris-i386-pc : numeric=
+ [ 0 -ne 0 ]
+ expr horology=horology-solaris-1947 : numeric=
+ [ 0 -ne 0 ]
+ expr tinterval=tinterval-solaris-1947 : numeric=
+ [ 0 -ne 0 ]
bestfile=
bestdiff=
result=2
+ [ ! -r ./expected/numeric.out ]
+ diff -w ./expected/numeric.out ./results/numeric.out
result=0
+ break
+ echo ok
ok
+ read line
+ [ 0 -ne 0 ]
+ [ -n 22844 ]
+ message shutting down postmaster
_dashes===
_spaces=
+ cut -c 1-38
+ echo shutting down postmaster
_msg=shutting down postmaster
+ echo == shutting down postmaster   
==
== shutting down postmaster   ==
+ kill -15 22844
+ unset postmaster_pid
+ rm -f /tmp/pg_regress.19030
+ cat ./regression.out
+ grep \.\.\.
+ sed s/ //g
+ wc -l
count_total=13
+ cat ./regression.out
+ grep \.\.\. ok
+ + wc -l sed
 s/ //g
count_ok=13
+ cat ./regression.out
+ sed s/ //g
+ wc -l
+ grep \.\.\. FAILED
count_failed=0
+ cat ./regression.out
+ grep \.\.\. failed (ignored)
+ sed s/ //g
+ wc -l
count_ignored=0
+ echo

+ [ 13 -eq 13 ]
msg=All 13 tests passed.
result=0
+ sed s/./=/g
+ echo  All 13 tests passed.
dashes===
+ echo ==
==
+ echo  All 13 tests passed.
 All 13 tests passed.
+ echo ==
==
+ echo

+ [ -s ./regression.diffs ]
+ rm -f ./regression.diffs ./regression.out
+ exit 0
+ exit
savestatus=0
+ [ -n  ]
+ rm -f /tmp/pg_regress.19030
+ exit 0

Hope that helps.


---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/users-lounge/docs/faq.html

Re: [HACKERS] RC1?

[Tom Lane]

"scott.marlowe" <[EMAIL PROTECTED]> writes:
> OK, make -x check fails, is there some other way to use -x I'm not 
> thinking of here?

I was thinking of running the script by hand, not via make:

/bin/sh -x ./pg_regress --temp-install --top-builddir=../../.. 
--schedule=./parallel_schedule --multibyte=SQL_ASCII

regards, tom lane

---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])

Re: [HACKERS] RC1?

[scott.marlowe]

On Tue, 12 Nov 2002, Tom Lane wrote:

> "scott.marlowe" <[EMAIL PROTECTED]> writes:
> > And then it stops.  Anyone know why it doesn't run the rest of the 
> > regresssion tests?  
> 
> Somebody else just reported the same thing on Solaris.  Must be
> something about the pg_regress script that doesn't play nicely with
> Solaris' shell.  Can you poke into it and try to figure out what?
> (Perhaps running the script with +x would help.)

OK, make -x check fails, is there some other way to use -x I'm not 
thinking of here?


---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster

Re: [HACKERS] RC1?

[scott.marlowe]

On Tue, 12 Nov 2002, Tom Lane wrote:

> "scott.marlowe" <[EMAIL PROTECTED]> writes:
> > And then it stops.  Anyone know why it doesn't run the rest of the 
> > regresssion tests?  
> 
> Somebody else just reported the same thing on Solaris.  Must be
> something about the pg_regress script that doesn't play nicely with
> Solaris' shell.  Can you poke into it and try to figure out what?
> (Perhaps running the script with +x would help.)

will do.


---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])

Re: [HACKERS] RC1?

[Tom Lane]

"scott.marlowe" <[EMAIL PROTECTED]> writes:
> And then it stops.  Anyone know why it doesn't run the rest of the 
> regresssion tests?  

Somebody else just reported the same thing on Solaris.  Must be
something about the pg_regress script that doesn't play nicely with
Solaris' shell.  Can you poke into it and try to figure out what?
(Perhaps running the script with +x would help.)

regards, tom lane

---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/users-lounge/docs/faq.html

Re: [HACKERS] RC1?

[scott.marlowe]

On 12 Nov 2002, Robert Treat wrote:

> On Tue, 2002-11-12 at 16:27, Tom Lane wrote:
> > Peter Eisentraut <[EMAIL PROTECTED]> writes:
> > > Bruce Momjian writes:
> > >> Are we ready for RC1 yet?
> > 
> > > Questionable.  We don't even have 50% confirmation coverage for the
> > > supported platforms yet.
> > 
> > We can't just wait around indefinitely for port reports that may or may
> > not ever appear.  In any case, most of the "<7.3" entries in the list
> > seem to be various flavors of *BSD; I think it's unlikely we broke
> > those ...
> 
> Why not send an email to the folks who last reported a supported
> platform and ask for an update? Probably won't get through to everyone,
> but it might help pare down the list of unconfirmed.

I get this for gmake check:

(Lotsa messages deleted):

== removing existing temp installation==
== creating temporary installation==
== initializing database system   ==
== starting postmaster==
running on port 65432 with pid 19771
== creating database "regression" ==
CREATE DATABASE
ALTER DATABASE
== dropping regression test user accounts ==
== installing PL/pgSQL==
== running regression test queries==
parallel group (13 tests):  float4 int8 text int2 oid int4 char boolean 
varchar name float8 bit numeric boolean  ... ok
 char ... ok
 name ... ok
 varchar  ... ok
 text ... ok
 int2 ... ok
 int4 ... ok
 int8 ... ok
 oid  ... ok
 float4   ... ok
 float8   ... ok
 bit  ... ok
 numeric  ... ok
== shutting down postmaster   ==

==
 All 13 tests passed.
==


rm regress.o
gmake[2]: Leaving directory 
`/home/smarlowe/postgresql-7.3b5/src/test/regress'
gmake[1]: Leaving directory `/home/smarlowe/postgresql-7.3b5/src/test'

(END QUOTE)

And then it stops.  Anyone know why it doesn't run the rest of the 
regresssion tests?  


---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])

Re: [HACKERS] RC1?

[scott.marlowe]

On 12 Nov 2002, Robert Treat wrote:

> On Tue, 2002-11-12 at 16:27, Tom Lane wrote:
> > Peter Eisentraut <[EMAIL PROTECTED]> writes:
> > > Bruce Momjian writes:
> > >> Are we ready for RC1 yet?
> > 
> > > Questionable.  We don't even have 50% confirmation coverage for the
> > > supported platforms yet.
> > 
> > We can't just wait around indefinitely for port reports that may or may
> > not ever appear.  In any case, most of the "<7.3" entries in the list
> > seem to be various flavors of *BSD; I think it's unlikely we broke
> > those ...
> 
> Why not send an email to the folks who last reported a supported
> platform and ask for an update? Probably won't get through to everyone,
> but it might help pare down the list of unconfirmed.

I'm testing x86 solaris right now.  It's turning into a giant pain because 
of how the box I'm on is configured.


---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster

Re: [HACKERS] RC1?

[Robert Treat]

On Tue, 2002-11-12 at 16:27, Tom Lane wrote:
> Peter Eisentraut <[EMAIL PROTECTED]> writes:
> > Bruce Momjian writes:
> >> Are we ready for RC1 yet?
> 
> > Questionable.  We don't even have 50% confirmation coverage for the
> > supported platforms yet.
> 
> We can't just wait around indefinitely for port reports that may or may
> not ever appear.  In any case, most of the "<7.3" entries in the list
> seem to be various flavors of *BSD; I think it's unlikely we broke
> those ...

Why not send an email to the folks who last reported a supported
platform and ask for an update? Probably won't get through to everyone,
but it might help pare down the list of unconfirmed.

Robert Treat




---(end of broadcast)---
TIP 6: Have you searched our list archives?

http://archives.postgresql.org