I agree, I did not realize that the yum repository I setup was still the development version, and that minor upgrades would render data directory incompatible. My bad.
All in all, I want to thank you all for quick responses, and for keeping PG software moving along. I've been using PG for over 5 years in multiple production environments, and it's been stable, fast, and easy to manage.
Looks like I jumped the gun with adding 8.4 development repository to yum updates, and that really was the cause of my minor pains.
K.
On Jun 16, 2009, at 10:07 AM, Tom Lane wrote:
Devrim GÜNDÜZ <
devrim@gunduz.org> writes:
Anyway, we are talking about an issue which should never ever happen, if
docs were read. I announced -devel RPMs lots of times, and each one
included a notice for dump/reload action.
I think the real issue here is that the OP was confused about whether
the devel RPMs represented a playpen or something that could be used for
production data. It's hard to say whether we didn't convey that message
clearly enough, or he failed to pay enough attention, but probably some
blame can be assigned on both sides of that.
regards, tom lane
--
Sent via pgsql-admin mailing list (
pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
