PostgreSQL v7.4 Release Candidate 1 [英] PostgreSQL v7.4 Release Candidate 1
问题描述
经过相对较短的beta5期间，没有出现任何重大事件，我们
刚刚打包我们的第一个候选版本为v7.4，希望
在接下来的7到14天内发布完整版本。
Beta5和RC1之间只有一个重大变化，到目前为止，还有/>
已报告回... RC1将不再适用于TCL8.0.x，因为对pgtclCmds.c的更改为
：
使用Tcl ByteArray对象来避免不需要的字符集在libpgtcl的lo_read / lo_write命令中进行
转换。另外，从lo_read（）返回失败，正确处理
。 ljb和Tom Lane。
还有一些其他的变化，影响了RI，Java和ECPG，
等等，有一个完整的列表可用的更改：
ftp://ftp.postgresql.org/pub/sources...g.BETA5.to.RC1
因为我们在家里伸展对于完整版本，我们鼓励多达
来测试和报告他们可以找到的任何错误，无论是作为
构建过程的一部分，还是以b $运行。现实生活场景。
如果我们在星期四午夜之前没有收到任何报告，我们会在完整的代码冻结中查看
，最终版本发布到发生在以下
周一。
------------------------ ---（播出结束）---------------------------
提示7：不要忘记增加你的可用空间地图设置
引用Marc G. Fournier < sc ***** @ postgresql.org>：
经过相对较短的beta5期间，没有出现任何重大事件，我们只有打包我们的第一个版本候选版本为v7.4，希望在未来7到14天内完整发布。
Beta5和RC1之间只有一个重大变化到目前为止，已经报告了......由于对pgtclCmds.c的更改，RC1将不再适用于TCL8.0.x：
使用Tcl ByteArray对象避免了libpgtcl'的lo_read / lo_write命令中不需要的字符集转换。此外，正确处理从lo_read（）返回的失败。 ljb和Tom Lane。
还有一些其他的变化，影响了RI，Java和ECPG，
等等，并提供了完整的变更列表：
ftp：// ftp.postgresql.org/pub/sources...g.BETA5.to.RC1
由于我们处于完整版本的主页，我们鼓励尽可能多的人/>可以测试和报告他们可以找到的任何错误，无论是作为构建过程的一部分，还是在现实生活中运行。场景。
如果我们在周四午夜之前没有收到任何报告，我们正在寻找完整的代码冻结，并在下面发布最终版本
星期一。
---------------------------（广播结束）-------- -------------------
提示7：别忘了增加免费空间地图设置
有人告诉我周末给你发电子邮件（或清单）。我刚拿到两个
的P4盒子，第一件事就是beta5，所以我可以玩pgbench和其他一些东西让我的脚湿透了。 ..但是有一个
的小声音说，也许我应该等。 :)
*快乐7.4几乎是发布舞蹈*
希望本周我会得到一些游戏时间。
-
Keith C. Perry
网络总监&申请
VCSN，Inc。
http://vcsn.com
____________________________________
此电子邮件帐户由以下人员主持：
VCSN，Inc： http://vcsn.com
---------- -----------------（广播结束）---------------------------
提示3：如果通过Usenet发布/阅读，请发送适当的
subscribe-nomail命令到 ma ******* @ postgresql.org ，以便您的
消息可以干净地通过邮件列表
>>>>> " MGF" == Marc G Fournier< sc ***** @ postgresql.org>写道：
MGF>由于我们处于完整版本的主页，因此我们鼓励尽可能多的购买MGF>可以测试和报告他们可以找到的任何错误，无论是作为
MGF>的一部分。构建过程，或在现实生活中运行场景。
MGF>如果我们在星期四午夜之前没有收到任何报告，我们正在寻找
MGF>在完整的代码冻结，最终版本发生在以下
MGF>星期一。
这是否现在不再需要initdb？
-
= - = - = - = - = - = - = - = - = - = - = - = - = - = - = - = - = - = - = - = - = - = - = - = - = - = - = - = - = - = - = - = - = - = - =
Vivek Khera，Ph.D。 Khera Communications，Inc。
互联网： kh***@kciLink.com Rockville，MD + 1- 240-453-8497
AIM：vivekkhera Y !: vivek_khera http://www.khera.org/~vivek/
--------------------- ------（播出结束）---------------------------
提示2：你可以使用取消注册命令一次性取消所有列表
（发送取消注册YourEmailAddressHere到 ma * ******@postgresql.org ）
星期二，4 2003年11月，Vivek Khera写道：
>> " MGF" == Marc G Fournier< sc ***** @ postgresql.org>写道：
MGF>由于我们处于完整版本的主页，我们鼓励尽可能多的MGF>可以测试和报告他们可以找到的任何错误，无论是作为MGF>的一部分。构建过程，或在现实生活中运行场景。
MGF>如果我们在周四午夜之前没有收到任何报告，我们正在寻找MGF>在完整的代码冻结，最终版本发生在以下
MGF>星期一。
这现在不再需要initdb吗？
我不想说*保证*，但它会是一个helluva bug需要
固定才需要它...
-------------------- -------（播出结束）---------------------------
提示1：订阅和取消订阅命令转到 ma*******@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
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
>>>>> "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)
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
这篇关于PostgreSQL v7.4 Release Candidate 1的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
