scrappy@postgresql.org (Marc G. Fournier) writes:
> configure (r1.570 -> r1.571)
> (http://developer.postgresql.org/cvsw...1.570&r2=1.571)

It appears that Marc has got autoconf 2.61 installed now, instead of the
2.59 that we've been using for some time. I'm a bit concerned about the
implications of switching to a version that's got zero track record for
us, and that AFAIK no other committers have installed. I'd rather see
a switch happen at the start of a devel cycle than at beta3; and in any
case it's got to be coordinated so that what is in the release doesn't
vary depending on who committed last.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


'k, 2.59 isn't even available in FreeBSD ports anymore, only 2.13 and 2.61, so
can someone else please run autoconf and commit, and I'll re-tag ...

- --On Thursday, November 15, 2007 23:37:22 -0500 Tom Lane <tgl@sss.pgh.pa.us>
wrote:

> scrappy@postgresql.org (Marc G. Fournier) writes:
>> configure (r1.570 -> r1.571)
>> (http://developer.postgresql.org/cvsw...igure?r1=1.570
>> &r2=1.571)
>
> It appears that Marc has got autoconf 2.61 installed now, instead of the
> 2.59 that we've been using for some time. I'm a bit concerned about the
> implications of switching to a version that's got zero track record for
> us, and that AFAIK no other committers have installed. I'd rather see
> a switch happen at the start of a devel cycle than at beta3; and in any
> case it's got to be coordinated so that what is in the release doesn't
> vary depending on who committed last.
>
> regards, tom lane



- ----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email . scrappy@hub.org MSN . scrappy@hub.org
Yahoo . yscrappy Skype: hub.org ICQ . 7615664
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4 (FreeBSD)

iD8DBQFHPSCd4QvfyHIvDvMRApMlAJsFhy+DGsSXMzy6bH0FAE Ql11zBKwCfbIQ6
66Upa6SjHDUccKm+Mun/l+g=
=rNQj
-----END PGP SIGNATURE-----


---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match

Tom Lane wrote:
> scrappy@postgresql.org (Marc G. Fournier) writes:
>> configure (r1.570 -> r1.571)
>> (http://developer.postgresql.org/cvsw...1.570&r2=1.571)
>
> It appears that Marc has got autoconf 2.61 installed now, instead of the
> 2.59 that we've been using for some time. I'm a bit concerned about the
> implications of switching to a version that's got zero track record for
> us, and that AFAIK no other committers have installed. I'd rather see
> a switch happen at the start of a devel cycle than at beta3; and in any
> case it's got to be coordinated so that what is in the release doesn't
> vary depending on who committed last.

O.k., so what do you want to do? Or more to the point, is there
something I can help with? I have machines with 2.59... Marc do you have
any left with 2.59?

Sincerely,

Joshua D. Drake

>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend
>


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

Marc G. Fournier wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
> 'k, 2.59 isn't even available in FreeBSD ports anymore, only 2.13 and 2.61, so
> can someone else please run autoconf and commit, and I'll re-tag ...
>

I can't commit but I can give access to a 2.59 version...

Sincerely,

Joshua D. Drake

> - --On Thursday, November 15, 2007 23:37:22 -0500 Tom Lane <tgl@sss.pgh.pa.us>
> wrote:
>
>> scrappy@postgresql.org (Marc G. Fournier) writes:
>>> configure (r1.570 -> r1.571)
>>> (http://developer.postgresql.org/cvsw...igure?r1=1.570
>>> &r2=1.571)
>> It appears that Marc has got autoconf 2.61 installed now, instead of the
>> 2.59 that we've been using for some time. I'm a bit concerned about the
>> implications of switching to a version that's got zero track record for
>> us, and that AFAIK no other committers have installed. I'd rather see
>> a switch happen at the start of a devel cycle than at beta3; and in any
>> case it's got to be coordinated so that what is in the release doesn't
>> vary depending on who committed last.
>>
>> regards, tom lane
>
>
>
> - ----
> Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
> Email . scrappy@hub.org MSN . scrappy@hub.org
> Yahoo . yscrappy Skype: hub.org ICQ . 7615664
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.4 (FreeBSD)
>
> iD8DBQFHPSCd4QvfyHIvDvMRApMlAJsFhy+DGsSXMzy6bH0FAE Ql11zBKwCfbIQ6
> 66Upa6SjHDUccKm+Mun/l+g=
> =rNQj
> -----END PGP SIGNATURE-----
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
> choose an index scan if your joining column's datatypes do not
> match
>


---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



- --On Thursday, November 15, 2007 20:49:04 -0800 "Joshua D. Drake"
<jd@commandprompt.com> wrote:

> Marc G. Fournier wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>>
>> 'k, 2.59 isn't even available in FreeBSD ports anymore, only 2.13 and 2.61,
>> so can someone else please run autoconf and commit, and I'll re-tag ...
>>
>
> I can't commit but I can give access to a 2.59 version...

Well, easiest is for Tom to run autoconf 2.59 and commit ... or Bruce ...

- ----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email . scrappy@hub.org MSN . scrappy@hub.org
Yahoo . yscrappy Skype: hub.org ICQ . 7615664
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4 (FreeBSD)

iD8DBQFHPSIc4QvfyHIvDvMRAoZCAJ9MF5wdAcB0aUTyT8qo62 +DF61wywCfQLJF
kSsl+ZTYu9SC+OEuA2NGPfU=
=EDTa
-----END PGP SIGNATURE-----


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

http://archives.postgresql.org

Marc G. Fournier wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
>
> - --On Thursday, November 15, 2007 20:49:04 -0800 "Joshua D. Drake"
> <jd@commandprompt.com> wrote:
>
>> Marc G. Fournier wrote:
>>> -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA1
>>>
>>>
>>> 'k, 2.59 isn't even available in FreeBSD ports anymore, only 2.13 and 2.61,
>>> so can someone else please run autoconf and commit, and I'll re-tag ...
>>>
>> I can't commit but I can give access to a 2.59 version...
>
> Well, easiest is for Tom to run autoconf 2.59 and commit ... or Bruce ...
>

*shrug* helping where I can... number is on pmt if you need me

Joshua D. Drake

> - ----
> Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
> Email . scrappy@hub.org MSN . scrappy@hub.org
> Yahoo . yscrappy Skype: hub.org ICQ . 7615664
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.4 (FreeBSD)
>
> iD8DBQFHPSIc4QvfyHIvDvMRAoZCAJ9MF5wdAcB0aUTyT8qo62 +DF61wywCfQLJF
> kSsl+ZTYu9SC+OEuA2NGPfU=
> =EDTa
> -----END PGP SIGNATURE-----
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Have you searched our list archives?
>
> http://archives.postgresql.org
>


---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend

"Marc G. Fournier" <scrappy@hub.org> writes:
> 'k, 2.59 isn't even available in FreeBSD ports anymore, only 2.13 and 2.61, so
> can someone else please run autoconf and commit, and I'll re-tag ...

Done

regards, tom lane

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

Tom Lane wrote:
> "Marc G. Fournier" <scrappy@hub.org> writes:
>> <jd@commandprompt.com> wrote:
>>> I can't commit but I can give access to a 2.59 version...
>
>> Well, easiest is for Tom to run autoconf 2.59 and commit ... or Bruce ...
>
> Locally I've got several autoconf versions installed so that I can
> update back-branch configure scripts properly. It'd probably be a good
> idea to improve your release scripts so that they select the "right"
> autoconf version for each release branch. You'll need multiple local
> installations though, instead of depending on freebsd ports for the
> "one true autoconf".
>
> Either that or we try to move up all supported back branches to the
> latest autoconf version; which might be a good idea but it scares me
> a bit.

I say have a VMWare instance running with the "one true" autoconf that
is currently accepted. That way we don't have to make that distinction.
Autoconf 2.59 is going to be predominantly in the wild (rhel 5, centos5
, dapper, debian) for at least another 3-4 years.

Joshua D. Drake

>
> regards, tom lane
>


---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match

"Marc G. Fournier" <scrappy@hub.org> writes:
> <jd@commandprompt.com> wrote:
>> I can't commit but I can give access to a 2.59 version...

> Well, easiest is for Tom to run autoconf 2.59 and commit ... or Bruce ...

Locally I've got several autoconf versions installed so that I can
update back-branch configure scripts properly. It'd probably be a good
idea to improve your release scripts so that they select the "right"
autoconf version for each release branch. You'll need multiple local
installations though, instead of depending on freebsd ports for the
"one true autoconf".

Either that or we try to move up all supported back branches to the
latest autoconf version; which might be a good idea but it scares me
a bit.

regards, tom lane

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

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



- --On Friday, November 16, 2007 00:03:46 -0500 Tom Lane <tgl@sss.pgh.pa.us>
wrote:

> "Marc G. Fournier" <scrappy@hub.org> writes:
>> <jd@commandprompt.com> wrote:
>>> I can't commit but I can give access to a 2.59 version...
>
>> Well, easiest is for Tom to run autoconf 2.59 and commit ... or Bruce ...
>
> Locally I've got several autoconf versions installed so that I can
> update back-branch configure scripts properly. It'd probably be a good
> idea to improve your release scripts so that they select the "right"
> autoconf version for each release branch. You'll need multiple local
> installations though, instead of depending on freebsd ports for the
> "one true autoconf".
>
> Either that or we try to move up all supported back branches to the
> latest autoconf version; which might be a good idea but it scares me
> a bit.

That would be a good idea, and really simply things ... FreeBSD seems to have
drop'd off support for all but 2.13 and 2.61 ...


- ----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email . scrappy@hub.org MSN . scrappy@hub.org
Yahoo . yscrappy Skype: hub.org ICQ . 7615664
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4 (FreeBSD)

iD8DBQFHPShG4QvfyHIvDvMRAm48AJ9D7FOT0EyASLJuBmxeLb E+464HdgCg54fJ
xQOk7rf3xBmwEreHKzlk3C4=
=6M0k
-----END PGP SIGNATURE-----


---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend