Re: [GENERAL] Moving from Java 1.5 to Java 1.6
Swayam Prakash Vemuri, 04.10.2012 08:52: Hi We have an application which uses postgresql 7.4.5. Now when we moved to Java 1.6, we are seeing lots of jdbc driver related compilation issues like shown at end of this email. Not only are you using an outdated (and unsupported) PostgreSQL version. You are also moving to a Java version that is soon to be de-supported. Why not move to 1.7 directly? -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] Moving from Java 1.5 to Java 1.6
On 10/04/12 11:21 PM, Thomas Kellerer wrote: You are also moving to a Java version that is soon to be de-supported. Java is supported? only if you mean the non-stop stream of updates brought on by web exploit exposures. if you're using Java as a server side application development environment, whats 'supported' mean ? frankly, at least from our perspective, Java 7 has been a no-fly so far. it brings nothing to the table we're interested in, just more Oracle induced nonsense. -- john r pierceN 37, W 122 santa cruz ca mid-left coast -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] Moving from Java 1.5 to Java 1.6
John R Pierce, 05.10.2012 08:34: You are also moving to a Java version that is soon to be de-supported. Java is supported? only if you mean the non-stop stream of updates brought on by web exploit exposures. Yes it is. In a similar way as PostgreSQL is supported. if you're using Java as a server side application development environment, whats 'supported' mean ? There are versions where Oracle will apply bugfixes and there are version where they will not. It's not only about security fixes for the Browser plugin-in (which I frankly think is totally useless), but there are also fixes to the whole JDK and Java API which could well affect server apps. Think IPv6 - AFAIK that will not be available for older Java versions. frankly, at least from our perspective, Java 7 has been a no-fly so far. it brings nothing to the table we're interested in, just more Oracle induced nonsense. I beg to differ. There are some new features in the language that are really nice. And also several new technologies will not be available on the old Java platforms (think Tomcat 7, JavaEE 6 and so on) The same way you should stay up-to-date with a PostgreSQL release you should with your Java development environment (even if you don't really need or use the new features) -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] Moving from Java 1.5 to Java 1.6
John R Pierce, 05.10.2012 08:34: On 10/04/12 11:21 PM, Thomas Kellerer wrote: You are also moving to a Java version that is soon to be de-supported. Java is supported? Found the link as well: http://www.oracle.com/technetwork/java/javase/eol-135779.html Quote: After February 2013, Oracle will no longer post updates of Java SE 6 to its public download sites -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] Moving from Java 1.5 to Java 1.6
On 10/04/2012 02:52 PM, Swayam Prakash Vemuri wrote: Hi We have an application which uses postgresql 7.4.5. Wow. Upgrade time on two levels: - You're running a fossilized point release. The latest 7.4.x is 7.4.30, 25 patch-levels after yours, and came out in October 2010 vs the August 2004 (!!) release date of your version. You're missing SIX YEARS OF BUG FIXES. - 7.4.x is unsupported. No future releases will be made with bug fixes or compatibility improvements. Upgrade urgently, because it's only going to get more difficult. Read the release notes from every .0 version between 7.4 and 9.1 or 9.2 to find possible compatibility issues you may face. Pay particular attention to the bytea_output change (if you use bytea), to standard_conforming_strings, and to the removal of implicit casts to text. Now when we moved to Java 1.6, we are seeing lots of jdbc driver related compilation issues like shown at end of this email. You shouldn't need to compile PgJDBC; there are pre-built binaries provided for JDBC3 and JDBC4 versions of the platform. You haven't said which version of PgJDBC you are updating *from* or *to*, making it hard to help you. The latest PgJDBC should be fine in Java 1.5, 1.6 or 1.7 and should work against Pg 8.3 or newer, and may also work on older versions of Pg as well. There's code in there for 7.3 and older. You cannot reasonably expect an ancient PgJDBC to compile on a new Java, or a new PgJDBC on a new Java to support a truly ancient Pg like 7.4. -- Craig Ringer -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] Moving from Java 1.5 to Java 1.6
On Thu, Oct 04, 2012 at 12:22:55PM +0530, Swayam Prakash Vemuri wrote: Hi We have an application which uses postgresql 7.4.5. You have a very large problem. The 7.4 series went out of support two years ago at 7.4.30, which means that you have known data corruption and crash bugs, and would even if you were to upgrade to 7.4.30 immediately. You need to upgrade to a supported version and put systems in place to do upgrades of every component in the system on a regular basis, as they all have finite lifetimes. Now when we moved to Java 1.6, we are seeing lots of jdbc driver related compilation issues like shown at end of this email. Those appear to be Java issues pretty strictly. Question is can we just only upgrade jdbc driver alone or its better to move completely to a new postgres version. ? Are there any docs that explain about how to migrate ? Use 9.2.1's pg_dump to get your data out of the running 7.4 database and then restore it to the 9.2.1 database. For each database on the 7.4 machine, run the following on the 9.2 machine: pg_dump -h name.of.7.4.machine.com -U postgres -Fc --file=mydb.dump mydb To restore on the 9.2 machine: pg_restore -C mydb.dump Hope this helps. Cheers, David. -- David Fetter da...@fetter.org http://fetter.org/ Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter Skype: davidfetter XMPP: david.fet...@gmail.com iCal: webcal://www.tripit.com/feed/ical/people/david74/tripit.ics Remember to vote! Consider donating to Postgres: http://www.postgresql.org/about/donate -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] Moving from Java 1.5 to Java 1.6
On 10/04/2012 10:13 AM, David Fetter wrote: For each database on the 7.4 machine, run the following on the 9.2 machine: pg_dump -h name.of.7.4.machine.com -U postgres -Fc --file=mydb.dump mydb Don't forget the global settings: pg_dumpall -g -U postgres -f globals.sql And you should probably restore it *before* the rest of the databases, since it contains users, groups, and so on, necessary for permissions to be correct following the database restore. pg_restore -U postgres globals.sql -- Shaun Thomas OptionsHouse | 141 W. Jackson Blvd. | Suite 500 | Chicago IL, 60604 312-444-8534 stho...@optionshouse.com __ See http://www.peak6.com/email_disclaimer/ for terms and conditions related to this email -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] Moving from Java 1.5 to Java 1.6
The appropriate list for this is the jdbc list: pgsql-j...@postgresql.org - Achilleas Mantzios IT DEPT
