By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
438,178 Members | 987 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 438,178 IT Pros & Developers. It's quick & easy.

PostgreSQL v7.4 Release Candidate 1

P: n/a

After a relatively short period for beta5, where nothing major arose, we
have just packaged up our first Release Candidate for v7.4, with the hopes
of producing a full release over the next 7 to 14 days.

There is only one major change between Beta5 and RC1 that, so far, has
been reported back ... RC1 will no longer work with TCL8.0.x, due to a
change to pgtclCmds.c:

Use Tcl ByteArray objects to avoid unwanted character set
translation in libpgtcl's lo_read/lo_write commands. Also, deal
correctly with failure return from lo_read(). ljb and Tom Lane.

There are a few other changes that were made, affecting RI, Java and ECPG,
among others, with a full list of changes available at:

ftp://ftp.postgresql.org/pub/sources...g.BETA5.to.RC1

As we are in the home stretch of a full release, we encourage as many as
possible to test and report any bugs they can find, whether as part of the
build process, or running in "real life" scenarios.

If we've heard no reports back before midnight on Thursday, we are looking
at a full code freeze, with a Final Release to happen on the following
Monday.

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

Nov 12 '05 #1
Share this Question
Share on Google+
14 Replies


P: n/a
Quoting "Marc G. Fournier" <sc*****@postgresql.org>:

After a relatively short period for beta5, where nothing major arose, we
have just packaged up our first Release Candidate for v7.4, with the hopes
of producing a full release over the next 7 to 14 days.

There is only one major change between Beta5 and RC1 that, so far, has
been reported back ... RC1 will no longer work with TCL8.0.x, due to a
change to pgtclCmds.c:

Use Tcl ByteArray objects to avoid unwanted character set
translation in libpgtcl's lo_read/lo_write commands. Also, deal
correctly with failure return from lo_read(). ljb and Tom Lane.

There are a few other changes that were made, affecting RI, Java and ECPG,
among others, with a full list of changes available at:

ftp://ftp.postgresql.org/pub/sources...g.BETA5.to.RC1

As we are in the home stretch of a full release, we encourage as many as
possible to test and report any bugs they can find, whether as part of the
build process, or running in "real life" scenarios.

If we've heard no reports back before midnight on Thursday, we are looking
at a full code freeze, with a Final Release to happen on the following
Monday.

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


Something told me to email you (or the list) over the weekend. I just got two
P4 boxes in and the first thing that went on there was beta5 so I could play
around with pgbench and some other things to get my feet wet... but there was a
little voice that was saying perhaps I should wait. :)

*happy 7.4 is almost released dance*
Hopefully I'll get some play time this week.
--
Keith C. Perry
Director of Networks & Applications
VCSN, Inc.
http://vcsn.com

____________________________________
This email account is being host by:
VCSN, Inc : http://vcsn.com

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

Nov 12 '05 #2

P: n/a
>>>>> "MGF" == Marc G Fournier <sc*****@postgresql.org> writes:

MGF> As we are in the home stretch of a full release, we encourage as many as
MGF> possible to test and report any bugs they can find, whether as part of the
MGF> build process, or running in "real life" scenarios.

MGF> If we've heard no reports back before midnight on Thursday, we are looking
MGF> at a full code freeze, with a Final Release to happen on the following
MGF> Monday.

Does this now guarentee no more initdb will be required?

--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Vivek Khera, Ph.D. Khera Communications, Inc.
Internet: kh***@kciLink.com Rockville, MD +1-240-453-8497
AIM: vivekkhera Y!: vivek_khera http://www.khera.org/~vivek/

---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to ma*******@postgresql.org)

Nov 12 '05 #3

P: n/a


On Tue, 4 Nov 2003, Vivek Khera wrote:
>> "MGF" == Marc G Fournier <sc*****@postgresql.org> writes:


MGF> As we are in the home stretch of a full release, we encourage as many as
MGF> possible to test and report any bugs they can find, whether as part of the
MGF> build process, or running in "real life" scenarios.

MGF> If we've heard no reports back before midnight on Thursday, we are looking
MGF> at a full code freeze, with a Final Release to happen on the following
MGF> Monday.

Does this now guarentee no more initdb will be required?


I hate to say *guarantee*, but it will be one helluva bug needing to be
fixed for it to be required ...
---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to ma*******@postgresql.org

Nov 12 '05 #4

P: n/a
Marc G. Fournier writes:
As we are in the home stretch of a full release, we encourage as many as
possible to test and report any bugs they can find, whether as part of the
build process, or running in "real life" scenarios.


Folks, we still need verification of PostgreSQL 7.4 on certain platforms.
See
<http://developer.postgresql.org/docs/postgres/supported-platforms.html>
for a list of what has already been tested. In particular, if you have
any of the following platforms available,

IRIX
NetBSD (anything but ix86)
OpenBSD (anything but ix86 and sparc)
SCO OpenServer

please get the release candidate tarball and run ./configure; make all;
make check; make install on them to see whether everything works. If you
have several compilers available (GCC and vendor compiler), try both.
Report the results together with `uname -a` to
pg***********@postgresql.org.

--
Peter Eisentraut pe*****@gmx.net
---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faqs/FAQ.html

Nov 12 '05 #5

P: n/a
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tuesday 04 November 2003 09:53 am, Peter Eisentraut wrote:
Marc G. Fournier writes:
As we are in the home stretch of a full release, we encourage as many as
possible to test and report any bugs they can find, whether as part of
the build process, or running in "real life" scenarios.


Folks, we still need verification of PostgreSQL 7.4 on certain platforms.
See
<http://developer.postgresql.org/docs/postgres/supported-platforms.html>
for a list of what has already been tested. In particular, if you have
any of the following platforms available,

IRIX
NetBSD (anything but ix86)
OpenBSD (anything but ix86 and sparc)
SCO OpenServer

^^^^^^^^^^^^^^^^^

Just a sarcastic remark: Should SCO be supported at all after what they are
doing ??

UC

- --
Open Source Solutions 4U, LLC 2570 Fleetwood Drive
Phone: +1 650 872 2425 San Bruno, CA 94066
Cell: +1 650 302 2405 United States
Fax: +1 650 872 2417
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE/p+5djqGXBvRToM4RAj5jAKDLvT1rhBKf30LQvXdbvs6ZI5C7fw CdGGCq
e6aNjbWUcwKawYoGRHOnmV4=
=R2ga
-----END PGP SIGNATURE-----
---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to ma*******@postgresql.org

Nov 12 '05 #6

P: n/a
El Mar 04 Nov 2003 14:53, Peter Eisentraut escribió:
Marc G. Fournier writes:
As we are in the home stretch of a full release, we encourage as many as
possible to test and report any bugs they can find, whether as part of the
build process, or running in "real life" scenarios.


Folks, we still need verification of PostgreSQL 7.4 on certain platforms.
See
<http://developer.postgresql.org/docs/postgres/supported-platforms.html>
for a list of what has already been tested. In particular, if you have
any of the following platforms available,

IRIX
NetBSD (anything but ix86)
OpenBSD (anything but ix86 and sparc)
SCO OpenServer

please get the release candidate tarball and run ./configure; make all;
make check; make install on them to see whether everything works. If you
have several compilers available (GCC and vendor compiler), try both.
Report the results together with `uname -a` to
pg***********@postgresql.org.


I saw that no body tried it on 64 bit Linux SPARC.

bugs:~# uname -a
Linux bugs 2.4.21 #1 Thu Aug 7 20:30:12 EDT 2003 sparc64 GNU/Linux

--
select 'mmarques' || '@' || 'unl.edu.ar' AS email;
-----------------------------------------------------------------
Martín Marqués | mm******@unl.edu.ar
Programador, Administrador, DBA | Centro de Telemática
Universidad Nacional
del Litoral
-----------------------------------------------------------------
---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to ma*******@postgresql.org

Nov 12 '05 #7

P: n/a
Martin Marques writes:
I saw that no body tried it on 64 bit Linux SPARC.

bugs:~# uname -a
Linux bugs 2.4.21 #1 Thu Aug 7 20:30:12 EDT 2003 sparc64 GNU/Linux


Well, I did build it on a machine whose uname looked much like this, but
it was in fact a 32-bit build. Are you sure yours was a 64-bit build?
(For example, long should be 8 bytes.)

--
Peter Eisentraut pe*****@gmx.net
---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faqs/FAQ.html

Nov 12 '05 #8

P: n/a
El Mar 04 Nov 2003 16:13, Peter Eisentraut escribió:
Martin Marques writes:
I saw that no body tried it on 64 bit Linux SPARC.

bugs:~# uname -a
Linux bugs 2.4.21 #1 Thu Aug 7 20:30:12 EDT 2003 sparc64 GNU/Linux


Well, I did build it on a machine whose uname looked much like this, but
it was in fact a 32-bit build. Are you sure yours was a 64-bit build?
(For example, long should be 8 bytes.)


Havn't built it yet, just got 7.4RC yestearday and thought about the 64 bit
build.
Are you saying it's not that all straight-forward to build a 64 bit
aplication, even having a 64 bit compiler, kernel, and, obviously,
architecture?

--
select 'mmarques' || '@' || 'unl.edu.ar' AS email;
-----------------------------------------------------------------
Martín Marqués | mm******@unl.edu.ar
Programador, Administrador, DBA | Centro de Telemática
Universidad Nacional
del Litoral
-----------------------------------------------------------------
---------------------------(end of broadcast)---------------------------
TIP 8: explain analyze is your friend

Nov 12 '05 #9

P: n/a
El Mar 04 Nov 2003 16:13, Peter Eisentraut escribió:
Martin Marques writes:
I saw that no body tried it on 64 bit Linux SPARC.

bugs:~# uname -a
Linux bugs 2.4.21 #1 Thu Aug 7 20:30:12 EDT 2003 sparc64 GNU/Linux


Well, I did build it on a machine whose uname looked much like this, but
it was in fact a 32-bit build. Are you sure yours was a 64-bit build?
(For example, long should be 8 bytes.)


Just got this from "configure":

checking whether long int is 64 bits... yes
checking for unsigned long... yes
checking size of unsigned long... 8
checking for short... yes
checking alignment of short... 2
checking for int... yes
checking alignment of int... 4
checking for long... yes
checking alignment of long... 8
checking for double... yes
checking alignment of double... 8

I think we have a 64 bit system here! :-)

--
select 'mmarques' || '@' || 'unl.edu.ar' AS email;
-----------------------------------------------------------------
Martín Marqués | mm******@unl.edu.ar
Programador, Administrador, DBA | Centro de Telemática
Universidad Nacional
del Litoral
-----------------------------------------------------------------
---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

http://archives.postgresql.org

Nov 12 '05 #10

P: n/a
SCO OpenServer

^^^^^^^^^^^^^^^^^

Just a sarcastic remark: Should SCO be supported at all after what they are
doing ??

I could see UnixWare but OpenServer is an end of life platform, it seems
odd that we would support
it. Regardless of the SCO/Caldera BS that is going on.

J

UC

- --
Open Source Solutions 4U, LLC 2570 Fleetwood Drive
Phone: +1 650 872 2425 San Bruno, CA 94066
Cell: +1 650 302 2405 United States
Fax: +1 650 872 2417
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE/p+5djqGXBvRToM4RAj5jAKDLvT1rhBKf30LQvXdbvs6ZI5C7fw CdGGCq
e6aNjbWUcwKawYoGRHOnmV4=
=R2ga
-----END PGP SIGNATURE-----
---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to ma*******@postgresql.org

--
Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC
Postgresql support, programming shared hosting and dedicated hosting.
+1-503-222-2783 - jd@commandprompt.com - http://www.commandprompt.com
Editor-N-Chief - PostgreSQl.Org - http://www.postgresql.org

---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to ma*******@postgresql.org

Nov 12 '05 #11

P: n/a


--On Tuesday, November 04, 2003 11:36:26 -0800 "Joshua D. Drake"
<jd@commandprompt.com> wrote:
SCO OpenServer

^^^^^^^^^^^^^^^^^

Just a sarcastic remark: Should SCO be supported at all after what they
are doing ??

I could see UnixWare but OpenServer is an end of life platform, it seems
odd that we would support
it. Regardless of the SCO/Caldera BS that is going on.

Actually, It's not. with the Legend Release (Due next year), it's getting
a major update.

I wouldn't say it's dead.

LER

J

UC

- --
Open Source Solutions 4U, LLC 2570 Fleetwood Drive
Phone: +1 650 872 2425 San Bruno, CA 94066
Cell: +1 650 302 2405 United States
Fax: +1 650 872 2417
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE/p+5djqGXBvRToM4RAj5jAKDLvT1rhBKf30LQvXdbvs6ZI5C7fw CdGGCq
e6aNjbWUcwKawYoGRHOnmV4=
=R2ga
-----END PGP SIGNATURE-----
---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to ma*******@postgresql.org

--
Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC
Postgresql support, programming shared hosting and dedicated hosting.
+1-503-222-2783 - jd@commandprompt.com - http://www.commandprompt.com
Editor-N-Chief - PostgreSQl.Org - http://www.postgresql.org
---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to ma*******@postgresql.org


--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 972-414-9812 E-Mail: le*@lerctr.org
US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)

iD8DBQE/qAEgrRNGhTxJvdYRAqleAJ47WTzL1iP2blfn6KHfSvSyP/z2XQCgn7Ko
YxYz0yat7QdUjlLbuHMIRkc=
=rjkk
-----END PGP SIGNATURE-----

Nov 12 '05 #12

P: n/a
ljb
sc*****@postgresql.org wrote:
...
There is only one major change between Beta5 and RC1 that, so far, has
been reported back ... RC1 will no longer work with TCL8.0.x, due to a
change to pgtclCmds.c:
...


I sent in a revised patch which removes the loss of Tcl8.0.x compatibility.
Guess it didn't make RC1. I doubt anyone cares about Tcl 8.0.x anymore, but
it would mean one less thing to document in the release notes.
Nov 12 '05 #13

P: n/a
ljb <lj****@mindspring.com> writes:
I sent in a revised patch which removes the loss of Tcl8.0.x compatibility.


When? I don't recall having seen any such patch.

regards, tom lane

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

Nov 12 '05 #14

P: n/a
ljb
tg*@sss.pgh.pa.us wrote:
ljb <lj****@mindspring.com> writes:
I sent in a revised patch which removes the loss of Tcl8.0.x compatibility.


When? I don't recall having seen any such patch.


I must be doing something wrong.

I can see my second patch on the news server news.us.postgresql.org as
message 196 in comp.databases.postgresql.interfaces.general, posted on Thu,
30 Oct 2003 01:17:41 +0000 (UTC). But it isn't showing up on the archive
of pgsql-interfaces on the web site. Other things I posted to the
interfaces group (like a beta release announcement of pgin.tcl for
PostgreSQL-7.4) also don't show up. But my posts to pgsql-bugs and
other groups are showing up in the archive. Is there a problem here? I did
notice that the mailing list name (pgsql-interfaces) does not match the
newsgroup (comp.databases.postgresql.interfaces.general).

I'll repost the patch on pgsql-patches. But it's going to be against
PostgreSQL-7.4beta5, not 7.4RC1, because I can't download RC1 from here.
If you need the patch against 7.4RC1, I should be able to get it in a few
days.
Nov 12 '05 #15

This discussion thread is closed

Replies have been disabled for this discussion.