Re: Best Current Pratice Postgres upgrade 6.5--7.2
On Thu, 2003-11-20 at 16:23, Monique Y. Herman wrote: On Thu, 20 Nov 2003 at 02:50 GMT, Henry Hollenberg penned: Hello, I have a database running on potato using postgres 6.5 that I'd like to upgrade to Woody running postgres 7.2. ... I believe the install notes say, somewhere, that it's best to do incremental jumps, so rather than doing 6.5-7.2 you would do every step in between. But my memory may be faulty ... A few weeks ago, I tried to convert my source install of 7.0 to 7.2, and even that seemed fraught with difficulty. To be honest, as I don't have an immediate need for a database, I ended up putting the conversion project on the back burner. I say in the migration notes that large version jumps may cause problems. However they are not guaranteed to cause problems. The main difficulty is that pg_dump has been buggy in the past. One important thing to remember is that you should keep your existing software available in case you need to go back. I think there may be places which still archive Debian packages of 6.5, but I don't have them any more myself, so it's wise to make sure you've got that software safe in case of need. If you need to provide a service, it's better to go back to an old version while you get things sorted out than disable the service altogether because you weren't prepared. If there are problems, they may come from things' being dumped in the wrong order. I don't think that a dump from 6.5 will contain bad SQL; as far as I can remember, incompatibiities in language are only found in earlier versions. All problems can be fixed by editing the dump file to make it valid; the only difficulty is where the mass of data is large so that the editing task is burdensome. If you upgrade =7.2 to =7.3 it is a good thing to run the contrib adddepends script, which will build the dependencies that are nowadays created automatically for such things as triggers. -- Oliver Elphick[EMAIL PROTECTED] Isle of Wight, UK http://www.lfix.co.uk/oliver GPG: 1024D/3E1D0C1C: CA12 09E0 E8D5 8870 5839 932A 614D 4C34 3E1D 0C1C A new commandment I give unto you; That ye love one another. As I have loved you, so ye also must love one another. By this shall all men know that ye are my disciples, if ye have love one to another. John 13:34,35 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Best Current Pratice Postgres upgrade 6.5--7.2
On Wed, Nov 19, 2003 at 06:50:19PM -0800, Henry Hollenberg wrote:
The docs seem to imply that upgrading with this big a jump from
6.5 to 7.2 is dangerous.even if I do it by hand like so:
pg_dump mydatabase dump.mydatabase
destroydb mydatabase
upgrade the database system to 7.2
createdb mydatabase
psql dump.mydatabase
as long as you have the dump of your database, you'll at least
be able to restore your old database on the older version of the
server.
the dump is all sql text, so you can make changes with an editor
(or perl for larger reformatting) to make it into what the newer
postgresql will accept.
--
}John Flinchbaugh{__
| [EMAIL PROTECTED] http://www.hjsoft.com/~glynis/ |
~~Powered by Linux: Reboots are for hardware upgrades only~~
signature.asc
Description: Digital signature
Re: Best Current Pratice Postgres upgrade 6.5--7.2
On Thu, 20 Nov 2003 at 02:50 GMT, Henry Hollenberg penned: Hello, I have a database running on potato using postgres 6.5 that I'd like to upgrade to Woody running postgres 7.2. The docs seem to imply that upgrading with this big a jump from 6.5 to 7.2 is dangerous.even if I do it by hand like so: pg_dump mydatabase dump.mydatabase destroydb mydatabase upgrade the database system to 7.2 createdb mydatabase psql dump.mydatabase Can this large jump be made safely? If not, I don't see any other versions of postgres available for debian...so how should it be done in smaller increments? Do my steps above look reasonable? Thanks, Henry Hollenberg [EMAIL PROTECTED] I believe the install notes say, somewhere, that it's best to do incremental jumps, so rather than doing 6.5-7.2 you would do every step in between. But my memory may be faulty ... A few weeks ago, I tried to convert my source install of 7.0 to 7.2, and even that seemed fraught with difficulty. To be honest, as I don't have an immediate need for a database, I ended up putting the conversion project on the back burner. -- monique PLEASE don't CC me. Please. Pretty please with sugar on top. Whatever it takes, just don't CC me! I'm already subscribed!! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Best Current Pratice Postgres upgrade 6.5--7.2
Hello, I have a database running on potato using postgres 6.5 that I'd like to upgrade to Woody running postgres 7.2. The docs seem to imply that upgrading with this big a jump from 6.5 to 7.2 is dangerous.even if I do it by hand like so: pg_dump mydatabase dump.mydatabase destroydb mydatabase upgrade the database system to 7.2 createdb mydatabase psql dump.mydatabase Can this large jump be made safely? If not, I don't see any other versions of postgres available for debian...so how should it be done in smaller increments? Do my steps above look reasonable? Thanks, Henry Hollenberg [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
