> Please read http://www.postgresql.org/support/versioning
Quoting part of the document:
Upgrading to a minor release does not require a dump and restore; merely stop
the database server, install the updated binaries, and restart the server.
For some releases, manual changes may be required to complete the upgrade, so
always read the release notes before upgrading.
=========
Thanx, Alvaro... looks like I can just change the binary and move clients to
7.3.18, with any database recreation and dump/restore. This I can do in the
patch itself.
So Alvaro/Tom, do you think 7.3.18 will get me on a lower risk of getting in
this situation?
-----Original Message-----
From: Alvaro Herrera [mailto:alvherre@commandprompt.com]
Sent: Friday, April 13, 2007 8:59 PM
To: Nitin Verma
Cc: Tom Lane; pgsql-general@postgresql.org
Subject: Re: [GENERAL] ERROR: XLogFlush: request
Nitin Verma wrote:
> Thanx Tom, anyway we are moving to 8.1.0 soon.
>
> Leaving that moving all our client to newer release will take sometime. I
> hope you know how it works in a product. Till that time we need to release
a
> patch that recovers from this condition.
>
> Said that, do we have some advice or workarounds?
Please read http://www.postgresql.org/support/versioning
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
