Does anyone know of any known issues (show-stoppers) with upgrading to
Postgresql 9.2 but retaining Postgis 1.5.3 or Postgis 1.5.5?
Thanks
In hibernate 3.3.2.GA, We previously utilized this java program to address
ingesting data into our PostgreSQL partitioned tables.
package im.empl.core.service.ingest.postgres;
import org.hibernate.Interceptor;
import org.hibernate.jdbc.Batcher;
import org.hibernate.jdbc.BatchingBatcherFactory;
-
From: jcasa...@systemguards.com.ec [mailto:jcasa...@systemguards.com.ec] On
Behalf Of Jaime Casanova
Sent: Tuesday, September 25, 2012 4:50 PM
To: Freddie Burgess
Cc: pgsql-bugs@postgresql.org
Subject: Re: [BUGS] Postgres Partitions not working with hibernate
4.1.6.Final
On Tue, Sep 25, 2012 at 3
programmatically.
Any workarounds to resolve this issue would be greatly appreciated.
thanks
-Original Message-
From: Craig Ringer [mailto:ring...@ringerc.id.au]
Sent: Tuesday, September 18, 2012 12:29 AM
To: Freddie Burgess
Cc: pgsql-bugs@postgresql.org
Subject: Re: [BUGS] Postgres JDBC-hibernate
-bugs-ow...@postgresql.org
[mailto:pgsql-bugs-ow...@postgresql.org] On Behalf Of Craig Ringer
Sent: Monday, September 17, 2012 12:39 AM
To: Freddie Burgess
Cc: pgsql-bugs@postgresql.org
Subject: Re: [BUGS] Postgres JDBC-hibernate Problem
On 09/12/2012 12:18 AM, Freddie Burgess wrote:
We have
We have upgraded from PostgreSQL 8.4.3 to PostgreSQL 9.1.4 and we are
getting the following errors when attempting to auto-gen schema DDL.
Old Configuration:
WEB-INF/lib/postgis-jdbc-1.3.3.jar,
WEB-INF/lib/postgis-stubs-1.3.3.jar,
WEB-INF/lib/postgresql-8.3-603.jdbc4.jar,
New Configuration:
We have successfully upgraded Postgresql from 8.4.3 to 9.1.4 in our
environment, but we have some questions/issues.
Before the upgrade:
Postgres8 data location -- /usr/local/pgsql/data --
/u01/fiber/postgres843/postgres_data
Postgres9 data location -- /opt/PostgreSQL/9.1/data --
Late yesterday afternoon our DB server went down hard. we tried to re-start
and it went into recovery mode to recover transaction history and failed.
Notable error was:
FATAL: failed to re-find parent key in index 257969064 for split pages
8366/12375
If you look this error up, it
We are trying to upgrade our production postgres database instance that is
approximately 4TB in size and it contains various table partition
structures.; a separate tablespace for each partition. We were initially
successful in performing the upgrade using pg_upgrade with both the link and
copy
