> However:
> <>http://www.postgresql.org/docs/7.4/static/release-7-4-2.html
> does say that dump/initdb/reload is an option to fix 2 errors.
> These two errors can also be fixed manually without dump / reload
> which is described in same URL.
>
Opps !! I was wrong and was in the impression
Vishal Kashyap @ [Sai Hertz And Control Systems] wrote:
Dear Rajesh ,
The release notes of upgrades usually indicate whether initdb
is required or not. Generally when the last digit of a version
change it does not require a dump and reload. In this case
the release notes say:
Dear Rajesh ,
> The release notes of upgrades usually indicate whether initdb
> is required or not. Generally when the last digit of a version
> change it does not require a dump and reload. In this case
> the release notes say:
>
> http://www.postgresql.org/docs/7.4/static/release.html#RELEAS
The release notes of upgrades usually indicate whether initdb
is required or not. Generally when the last digit of a version
change it does not require a dump and reload. In this case
the release notes say:
http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-5
E.1.1. Migration
DB created under 7.4.2 will work with 7.4.5, but I thing You should
backup your data before upgrading to a new version.
--
Best Regards,
Frans Gunawan
[EMAIL PROTECTED]
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
Will a DB created
under 7.4.2 work with 7.4.5, or do I need to back it up and restore it to a
newly created 7.5.4 DB?
Chris
White
