[YSQL] Creating table with duplicate name results in multiple YB tables

[ndeodhar]

If we create a duplicate table, then YSQL returns an error saying that table already exists, but yb master creates the table. For example:

yugabyte=# create table test(a int primary key);
CREATE TABLE
yugabyte=# create table test(a int primary key);
ERROR:  relation "test" already exists

Now, if you go to master UI, you'll see two tables with the name test.

This issue will get fixed once we have background job in master to delete such inconsistencies (rather the window during which the extra tables will exist will reduce). However, we should check if we can reorder the table creation process in YSQL such that table is created on master after constraint and sanity checks are done in postgres.

[marcus-sa]

Weird, I'm still getting this error using the latest version.
Here's the error that Keycloak outputs:

13:22:22,492 FATAL [org.keycloak.services] (ServerService Thread Pool -- 62) Error during startup: org.keycloak.connections.jpa.updater.liquibase.lock.LockRetryException: liquibase.exception.DatabaseException: ERROR: relation "databasechangeloglock" already exists [Failed SQL: CREATE TABLE public.databasechangeloglock (ID INT NOT NULL, LOCKED BOOLEAN NOT NULL, LOCKGRANTED TIMESTAMP WITHOUT TIME ZONE, LOCKEDBY VARCHAR(255), CONSTRAINT PK_DATABASECHANGELOGLOCK PRIMARY KEY (ID))]

[marcus-sa]

So, why is this still occurring?