# problem with liquibase, postgres and maven

**URL:** <https://forum.liquibase.org/t/problem-with-liquibase-postgres-and-maven/24>\
**Category:** General Discussion\
**Created:** [February 17, 2011, 6:14pm UTC](https://forum.liquibase.org/t/problem-with-liquibase-postgres-and-maven/24 "2011-02-17T18:14:00Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Guest](https://avatars.discourse-cdn.com/v4/letter/g/8dc957/32.png) [@Guest](https://forum.liquibase.org/u/Guest)\
**Post date:** [February 17, 2011, 6:14pm UTC](https://forum.liquibase.org/t/problem-with-liquibase-postgres-and-maven/24/1 "2011-02-17T18:14:00Z")

</div>

Hi there,  
  
I have a problem running maven’s liquibase-plugin on a postgresql-db. When trying to run liquibase:update from the command-line, I get the error message  
  
[ERROR] Failed to execute goal org.liquibase:liquibase-plugin:1.9.5.0:update (de fault-cli) on project backend-persistence: Error setting up or running Liquibase : liquibase.exception.JDBCException: Error executing SQL CREATE TABLE databasech angeloglock (ID INT NOT NULL, LOCKED BOOLEAN NOT NULL, LOCKGRANTED TIMESTAMP WIT H TIME ZONE, LOCKEDBY VARCHAR(255), CONSTRAINT PK\_DATABASECHANGELOGLOCK PRIMARY KEY (ID)): FEHLER: Relation +databasechangeloglock½ existiert bereits -\> [Help 1]  
  
simply dropping the db-table does not help, it looks like liquibase is creating it twice, as the logfile suggests:  
  
… CREATE TABLE databasechangeloglock (ID INT NOT NULL, LOCKED BOOLEAN NOT NULL, LOCKGRANTED TIMESTAMP WITH TIME ZONE, LOCKEDBY VARCHAR(255), CONSTRAINT PK\_DATABASECHANGELOGLOCK PRIMARY KEY (ID)) COMMIT BEGIN INSERT INTO databasechangeloglock (ID, LOCKED) VALUES (1, false) COMMIT BEGIN LECT NULL AS TABLE\_CAT, n.nspname AS TABLE\_SCHEM, c.relname AS TABLE\_NAME, CASE n.nspname … CREATE TABLE databasechangeloglock (ID INT NOT NULL, LOCKED BOOLEAN NOT NULL, LOCKGRANTED TIMESTAMP WITH TIME ZONE, LOCKEDBY VARCHAR(255), CONSTRAINT PK\_DATABASECHANGELOGLOCK PRIMARY KEY (ID)) FEHLER: Relation »databasechangeloglock« existiert bereits (already exists)  
  
Any ideas how to solve this problem?  
  
Thanks in advance,  
  
Matthias

---

<div class="post-metadata">

**Author:** ![taranenko](https://avatars.discourse-cdn.com/v4/letter/t/ee7513/32.png) [@taranenko](https://forum.liquibase.org/u/taranenko)\
**Post date:** [February 17, 2011, 6:14pm UTC](https://forum.liquibase.org/t/problem-with-liquibase-postgres-and-maven/24/2 "2011-02-17T18:14:00Z")

</div>

Mattias,

is a great reason using liquibase 1.9.x instead of last 2.0 version?