From: | Grzegorz Jaśkiewicz <gryzman(at)gmail(dot)com> |
---|---|
To: | Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | Devrim GÜNDÜZ <devrim(at)gunduz(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, jd(at)commandprompt(dot)com, Thomas Kellerer <spam_eater(at)gmx(dot)net>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: For production: 8.4 or 8.3? |
Date: | 2009-07-28 09:07:06 |
Message-ID: | 2f4958ff0907280207x6e7ce716g4d7f0cccdba5fa99@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I used pg_migrator to migrate my rather large production databases
(couple hundreds GBs). Schemas are easy, as I keep datetimes as
bigints myself (for various reasons) I won't get the float/int
problem.
But I do understand, that keeping dates as floats might cause grief
(unless you create operator that compares timestamps with cast to (0),
etc). But that's another storry.
I wouldn't be afraid to use 8.4. I am using cvs head of postgresql in
testing al the times since 8.1beta , and never had an issue (that
wasn't my own fault).
But goes without saying, every release has bugs, so sooner you test
it, sooner hackers can fix them, if you find one. So my suggestion,
migrate data, do preproduction tests, and stuff. Once you're happy, go
for 8.4
From | Date | Subject | |
---|---|---|---|
Next Message | Andreas Wenk | 2009-07-28 09:34:24 | Re: Video available for PGDay SJC '09 |
Previous Message | Sim Zacks | 2009-07-28 09:03:36 | count of query results in for loop |