BUG #12851: Failed to initial Jackrabbit JCR Repository

From: chhui(at)ps(dot)asl(dot)com(dot)hk
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #12851: Failed to initial Jackrabbit JCR Repository
Date: 2015-03-11 16:55:56
Message-ID: 20150311165556.4035.21117@wrigleys.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 12851
Logged by: Harry Hui
Email address: chhui(at)ps(dot)asl(dot)com(dot)hk
PostgreSQL version: 9.4.0
Operating system: Fedora 20 x86 64Bit
Description:

I had set up PostgreSQL 9.4 DBR version on Fedora 20. There are two
instances of PostgreSQL to perform the replication. This function was
working fine. However, I started a Jackrabbit JCR repository with
persistence manager
[org.apache.jackrabbit.core.persistence.bundle.PostgreSQLPersistenceManager].
It could not start with PostgreSQL DBR.
It throw exception below. This exception only happened in DBR version.
Normal PostgreSQL 4.0 is working fine with Jackrabbit.
11.03.2015 11:12:48 DEBUG localhost-startStop-1 [StatManager.init:48]
Started StatManager. QueryStat is enabled false
11.03.2015 11:12:48 INFO localhost-startStop-1 [RepositoryImpl.<init>:256]
Starting repository...
11.03.2015 11:13:06 ERROR localhost-startStop-1
[ConnectionHelper$RetryManager.doTry:548] Failed to execute SQL (stacktrace
on DEBUG log level): org.postgresql.util.PSQLException: ERROR: Cannot UPDATE
table repository_fsentry because it does not have primary key.
Hint: Add primary key to the table
11.03.2015 11:13:06 DEBUG localhost-startStop-1
[ConnectionHelper$RetryManager.doTry:549] Failed to execute SQL
org.postgresql.util.PSQLException: ERROR: Cannot UPDATE table
repository_fsentry because it does not have primary key.
Hint: Add primary key to the table

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message m40636067 2015-03-12 03:22:19 BUG #12853: Cannot install
Previous Message wnordmann 2015-03-11 16:35:10 BUG #12850: ANALYZE of big table is taking extreemly much memory