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 <chesterma...@gmail.com>wrote: > Beside all notes, i recommend you to use pg_upgrade, to avoid a complete > backup/restore in your transition. > > http://www.postgresql.org/docs/9.2/static/pgupgrade.html > > > On Fri, Apr 5, 2013 at 1:30 PM, Kevin Grittner <kgri...@ymail.com> wrote: > >> Robert Treat <r...@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 >> > >
