El mié, 11-03-2015 a las 16:55 +0000, chhui@ps.asl.com.hk escribió:
> The following bug has been logged on the website:
>
> Bug reference: 12851
> Logged by: Harry Hui
> Email address: chhui@ps.asl.com.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
This is not a postresql's bug, is only a restriction of BDR extension as
you can read in its wiki:
https://wiki.postgresql.org/wiki/BDR_Command_Restrictions#Replication_of_UPDATE_or_DELETE_on_a_table_without_a_PRIMARY_KEY
>
>
