From: | Hacksaw <hacksaw(at)hacksaw(dot)org> |
---|---|
To: | Lamar Owen <lamar(dot)owen(at)wgcr(dot)org> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Upgrading: So now you tell me!!?!? |
Date: | 2003-03-27 19:31:28 |
Message-ID: | 200303271931.h2RJVSBK005983@habitrail.home.fools-errant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
No worries, I do know what to do in essence. One question: is there anything
*special* I need to do? I notice a mention of needing to hand edit the
dumpfiles if upgrading from 7.2 to 7.3. Is this the case here as well? Where
is the documentation on that?
Let me say that despite the problems, I support your efforts. Being a
sys-admin, I understand that mistakes are made, and I'm cool with it. I mainly
wanted to help make sure someone with less experience and more at stake
doesn't get burned.
Is there a clear marker of file format version in the database files? My
suggestion would be to have the pre-install script test for that, and abort if
it's the wrong version. Then you have the README.upgrade say something like
"After you run pg_dumpall, move /var/lib/pqsql to /var/lib/pgsql.$OLD_VERSION_N
UMBER.
That way, the preinstall will find nothing, and be able to do initdb, and if
you are feeling really snarky, offer to try a restore for them.
--
Trust music.
http://www.hacksaw.org -- http://www.privatecircus.com -- KB1FVD
From | Date | Subject | |
---|---|---|---|
Next Message | philo vivero | 2003-03-27 20:05:08 | Re: PostgreSQL + IDS load/latency help |
Previous Message | Lamar Owen | 2003-03-27 19:08:59 | Re: Upgrading: So now you tell me!!?!? |