Обсуждение: converting older databases
Hi
When you install a newer version of Postgres how do you upgrade your database to the new format?
Apparantly you can't just backup the old database and restore it on the new software.
How do you do this on Windows?
Thanks
H.F.
When you install a newer version of Postgres how do you upgrade your database to the new format?
Apparantly you can't just backup the old database and restore it on the new software.
How do you do this on Windows?
Thanks
H.F.
Heine Ferreira wrote: > Hi > > When you install a newer version of Postgres how do you upgrade your > database to the new format? > Apparantly you can't just backup the old database and restore it on > the new software. > How do you do this on Windows? you pg_dump >dumpfile.sql the old one, psql -f dumpfile.sql to the new. Typically, you only need to do this between major upgrades, like 8.2.x to 8.3.y ... 8.3.x to 8.3.y doesn't require a dump/restore unless the release notes state otherwise (this has only happened a few times, I think there was a 8.0.1->8.0.N that required it due to a minor change required by a bugfix)
hai
Recently we migrated our database from 8.2.4 to 8.2.12 , went through manuals and followed the below steps
1.pg_dumpall to take data dump of current database
2.stopped database
3.moved the pgsql to backup folder
4.downloaded 8.2.12 , configured - gmake - gmake install
5.recreated cluster directory
6.restored the database with datadump
It was like complete re-installation process.
Can anyone explain a alternative method to upgrade a existing database
thanks in advance
regards
sathish
--
BSG LeatherLink Pvt Limited,
Mail To : sathish@leatherlink.net
Website : http://www.leatherlink.net
Contact : +91 44 65191757
Recently we migrated our database from 8.2.4 to 8.2.12 , went through manuals and followed the below steps
1.pg_dumpall to take data dump of current database
2.stopped database
3.moved the pgsql to backup folder
4.downloaded 8.2.12 , configured - gmake - gmake install
5.recreated cluster directory
6.restored the database with datadump
It was like complete re-installation process.
Can anyone explain a alternative method to upgrade a existing database
thanks in advance
regards
sathish
On Fri, Mar 6, 2009 at 12:28 AM, John R Pierce <pierce@hogranch.com> wrote:
you pg_dump >dumpfile.sql the old one, psql -f dumpfile.sql to the new.Heine Ferreira wrote:Hi
When you install a newer version of Postgres how do you upgrade your database to the new format?
Apparantly you can't just backup the old database and restore it on the new software.
How do you do this on Windows?
Typically, you only need to do this between major upgrades, like 8.2.x to 8.3.y ... 8.3.x to 8.3.y doesn't require a dump/restore unless the release notes state otherwise (this has only happened a few times, I think there was a 8.0.1->8.0.N that required it due to a minor change required by a bugfix)
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
--
BSG LeatherLink Pvt Limited,
Mail To : sathish@leatherlink.net
Website : http://www.leatherlink.net
Contact : +91 44 65191757
Sathish Duraiswamy wrote: > hai > > Recently we migrated our database from 8.2.4 to 8.2.12 , went through > manuals and followed the below steps > > 1.pg_dumpall to take data dump of current database > 2.stopped database > 3.moved the pgsql to backup folder > 4.downloaded 8.2.12 , configured - gmake - gmake install > 5.recreated cluster directory > 6.restored the database with datadump > > It was like complete re-installation process. > > Can anyone explain a alternative method to upgrade a existing database details vary with platform and how postgresql was installed in the first place. with a 8.2.x install from the pgdg82 yum repositories on a rhel/centos/fedora platform $ yum upgrade postgresql-server would have sufficed. its only necessary to dump/restore when going between major versions (8.2.x to 8.3.x, for instance), or when making architecture changes (x86_32 to x86_64, or float timestamp to integer timestamp).
Thanks for ur reply John
For information , We have Novell SuSe 11.0 server ON x86_32 and we have installed from source code
Regards
sathish
--
BSG LeatherLink Pvt Limited,
Mail To : sathish@leatherlink.net
Website : http://www.leatherlink.net
Contact : +91 44 65191757
For information , We have Novell SuSe 11.0 server ON x86_32 and we have installed from source code
Regards
sathish
On Fri, Mar 6, 2009 at 1:46 AM, John R Pierce <pierce@hogranch.com> wrote:
Sathish Duraiswamy wrote:details vary with platform and how postgresql was installed in the first place. with a 8.2.x install from the pgdg82 yum repositories on a rhel/centos/fedora platformhai
Recently we migrated our database from 8.2.4 to 8.2.12 , went through manuals and followed the below steps
1.pg_dumpall to take data dump of current database
2.stopped database
3.moved the pgsql to backup folder
4.downloaded 8.2.12 , configured - gmake - gmake install
5.recreated cluster directory
6.restored the database with datadump
It was like complete re-installation process.
Can anyone explain a alternative method to upgrade a existing database
$ yum upgrade postgresql-server
would have sufficed. its only necessary to dump/restore when going between major versions (8.2.x to 8.3.x, for instance), or when making architecture changes (x86_32 to x86_64, or float timestamp to integer timestamp).
--
BSG LeatherLink Pvt Limited,
Mail To : sathish@leatherlink.net
Website : http://www.leatherlink.net
Contact : +91 44 65191757
On Thu, Mar 5, 2009 at 5:56 PM, Sathish Duraiswamy <sathish@leatherlink.net> wrote: > Thanks for ur reply John > > For information , We have Novell SuSe 11.0 server ON x86_32 and we have > installed from source code Then all you need to do is run ./configure with the same --prefix switch as you did before, and then make ; make install it and it will be installed over the top of the pg install files already there. Shut down the db first, then run make install. Should come right back up. It's always a good idea to have a backup just in case though.