New shapshot RPMs (Sep 7 2008) are ready for testing
Hi,
I just released new RPM sets, which is based on today's CVS snapshot
(Sep 7, 12:00AM PDT).
These packages *do* require a dump/reload, even from previous 8.4
packages, since I now enabled --enable-integer-datetimes in PGDG RPMs by
default (and IIRC there is a catversion update in recent commits, too
lazy to check it now :) ).
The previous package sets were tested by ~150 people. Thanks for the
interest on these packages, and I hope we will continue helping
development of PostgreSQL more.
As usual, please find detailed info from:
A mini howto about 8.4devel release + RPMs is here:
http://yum.pgsqlrpms.org/news-8.4devel-ready-for-testing.php
The tarball I used is here:
http://yum.pgsqlrpms.org/srpms/8.4
(I will remove this tarball after a few weeks...)
Please report any packaging related errors to me. If you find any
PostgreSQL 8.4 bugs, please post them to pgsql-bugs@PostgreSQL.org or
fill out this form:
http://www.postgresql.org/support/submitbug
Regards,
--
Devrim GÜNDÜZ, RHCE
devrim~gunduz.org, devrim~PostgreSQL.org, devrim.gunduz~linux.org.tr
http://www.gunduz.org
Devrim GÜNDÜZ wrote:
Hi,
I just released new RPM sets, which is based on today's CVS snapshot
(Sep 7, 12:00AM PDT).These packages *do* require a dump/reload, even from previous 8.4
packages, since I now enabled --enable-integer-datetimes in PGDG RPMs by
default (and IIRC there is a catversion update in recent commits, too
lazy to check it now :) ).
Hasn't integer-datetimes been the default for a while? Of course, a
catversion bump will force a dump/reload regardless of that.
cheers
andrew
Hello,
On Sun, 2008-09-07 at 11:01 -0400, Andrew Dunstan wrote:
Hasn't integer-datetimes been the default for a while?
No. I added it as a macro to 8.3, but did not enable it by default,
because I am trying to be binary compatible with Red Hat / Fedora RPMs.
I believe Tom will also add it to 8.4 packages for Fedora 11.
Regards,
--
Devrim GÜNDÜZ, RHCE
devrim~gunduz.org, devrim~PostgreSQL.org, devrim.gunduz~linux.org.tr
http://www.gunduz.org
Andrew Dunstan wrote:
Hasn't integer-datetimes been the default for a while? Of course, a
catversion bump will force a dump/reload regardless of that.
Unfortunately not. It is the default on some versions of linux such as
Debian/Ubuntu.
Sincerely,
Joshua D. Drake
Devrim =?ISO-8859-1?Q?G=DCND=DCZ?= <devrim@gunduz.org> writes:
On Sun, 2008-09-07 at 11:01 -0400, Andrew Dunstan wrote:
Hasn't integer-datetimes been the default for a while?
No. I added it as a macro to 8.3, but did not enable it by default,
because I am trying to be binary compatible with Red Hat / Fedora RPMs.
I believe Tom will also add it to 8.4 packages for Fedora 11.
The RHEL/Fedora RPMs have never specified this one way or the other,
so they'd just get the default. I haven't really thought about whether
to change that when 8.4 comes out. I'd prefer to follow upstream's
lead on the point; but if for instance we could do update-in-place
so long as you hadn't switched datetime representation, that would be a
pretty powerful incentive to stick with the float format.
regards, tom lane
Joshua D. Drake wrote:
Andrew Dunstan wrote:
Hasn't integer-datetimes been the default for a while? Of course, a
catversion bump will force a dump/reload regardless of that.Unfortunately not. It is the default on some versions of linux such as
Debian/Ubuntu.
The point I was making is that for 8.4, unless you specifically
configure with --disable-integer-datetimes, it is enabled by default on
any platform that can support it. We committed that change on 30 March
here: http://archives.postgresql.org/pgsql-committers/2008-03/msg00550.php
cheers
andrew
Hi,
On Sun, 2008-09-07 at 13:39 -0400, Andrew Dunstan wrote:
The point I was making is that for 8.4, unless you specifically
configure with --disable-integer-datetimes, it is enabled by default on
any platform that can support it. We committed that change on 30 March
here: http://archives.postgresql.org/pgsql-committers/2008-03/msg00550.php
You are right, and I overlooked the actual macro.
I now "fixed" the macro by changing its behavior to use the
--disable-integer-datetimes mode if not defined.
Cheers,
--
Devrim GÜNDÜZ, RHCE
devrim~gunduz.org, devrim~PostgreSQL.org, devrim.gunduz~linux.org.tr
http://www.gunduz.org