Fwd: upgrading from V8.3.4 to V9.2.4 - Mailing list pgsql-general

From Ian Harding
Subject Fwd: upgrading from V8.3.4 to V9.2.4
Date
Msg-id CAMR4UwHGwowdLztLx0FJ4BcdgobCzzibET6YW-9gkk78CtQh1A@mail.gmail.com
Whole thread Raw
In response to upgrading from V8.3.4 to V9.2.4  (Paul Tilles <paul.tilles@noaa.gov>)
List pgsql-general
Forgot to include the list!  Sorry!
If you have a non-standard socket file location pg_upgrade will not work for this upgrade.


On Fri, Apr 5, 2013 at 9:37 AM, Leonardo Carneiro <chesterman86@gmail.com> wrote:
Beside all notes, i recommend you to use pg_upgrade, to avoid a complete backup/restore in your transition.



On Fri, Apr 5, 2013 at 1:30 PM, Kevin Grittner <kgrittn@ymail.com> wrote:
Robert Treat <rob@xzilla.net> wrote:

> Yeah, there were also some subtle breakage around keywords used
> as variable naming when plpgsql was port to use the core lexer.

One more: from a Java client access to bytea columns will break if
you don't also use the latest JDBC driver jar.

--
Kevin Grittner
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general



pgsql-general by date:

Previous
From: Albe Laurenz
Date:
Subject: Re: dataset lock
Next
From: "wk"
Date:
Subject: =?gb18030?B?u9i4tKO6IFtHRU5FUkFMXSBjb25maWd1cmUgIC0t?= =?gb18030?B?ZW5hYmxlIC1kdHJhY2Ugo6hzeXN0ZW10YXCjqSBv?= =?gb18030?B?biBjZW50b3M2LjQgeDg2XzMyNzd5TUwzVnpjaTlp?= =?gb18030?B?YVc0dmMzUmhjRG8gaW52YWxpZCBvcHRpb24gLS0g?= =?gb18030?B?J0Mn?=