Prisma•3mo ago•

2 replies

Shadow database issues with extensions

ORM

Hi, I've a database that uses

pg_partman

pg_partman

and

pg_cron

pg_cron

extensions.

The problems are that

pg_cron

pg_cron

only runs on the db that is configured in

cron.database_name

cron.database_name

postgres config file. So everytime the migration that runs

CREATE EXTENSION IF NOT EXISTS pg_cron;

CREATE EXTENSION IF NOT EXISTS pg_cron;

fails because it can not be applied to the shadow db. To solve this I've set up another DB to use as shadow.

Problem now is that

pg_partman

pg_partman

and

pg_cron

pg_cron

use their own schemas to work so the

soft reset

soft reset

that

migrate dev

migrate dev

performs on my custom shadow database does not drop the whole database so I still have issues because partman and cron schemas does not get "reset" and I have errors like

duplicate key value violates unique constraint "part_config_parent_table_pkey"

duplicate key value violates unique constraint "part_config_parent_table_pkey"

because the migration tries to insert something that already exists.

Prisma•3mo ago•

2 replies

Somacortoi

Shadow database issues with extensions

ORM

Hi, I've a database that uses

pg_partman

pg_partman

and

pg_cron

pg_cron

extensions.

The problems are that

pg_cron

pg_cron

only runs on the db that is configured in

cron.database_name

cron.database_name

postgres config file. So everytime the migration that runs

CREATE EXTENSION IF NOT EXISTS pg_cron;

CREATE EXTENSION IF NOT EXISTS pg_cron;

fails because it can not be applied to the shadow db. To solve this I've set up another DB to use as shadow.

Problem now is that

pg_partman

pg_partman

and

pg_cron

pg_cron

use their own schemas to work so the

soft reset

soft reset

that

migrate dev

migrate dev

performs on my custom shadow database does not drop the whole database so I still have issues because partman and cron schemas does not get "reset" and I have errors like

duplicate key value violates unique constraint "part_config_parent_table_pkey"

duplicate key value violates unique constraint "part_config_parent_table_pkey"

because the migration tries to insert something that already exists.

Shadow database issues with extensions

Similar Threads

Shadow database issues with extensions

Similar Threads

Similar Threads

Similar Threads