| From: | veem v <veema0000(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Issue during partition drop |
| Date: | 2026-04-30 02:37:21 |
| Message-ID: | CAB+=1TVS7o=uBorTNjXHzhLO3pJQOwZOYDWoGMJFqLTc9S8ZRw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi,
We have the Aurora Postgres database. And for a table with PK-FK
relationships, we have been running into issues while dropping partitions
using partman. We have planned to detach and drop the partitions but end up
with the below error , so wanted to understand, if this is expected
behaviour and how to handle it?
ERROR: cannot drop table <table_name>_p20250202 because other objects
depend on it
CONTEXT: SQL statement "DROP TABLE <table_name>_p20250202"
PL/pgSQL function
drop_partition_time(text,interval,boolean,boolean,text,timestamp with time
zone) line 250 at EXECUTE
PL/pgSQL function partman.run_maintenance(text,boolean,boolean) line 336 at
assignment
DETAIL: constraint <constraint_name>_fkey on table <table_name> depends on
table <table_name>_p20250202
Regards
Veem
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matt Magoffin | 2026-04-30 02:48:32 | Re: Confirmation on concurrent SELECT FOR UPDATE with ON CONFLICT DO NOTHING |
| Previous Message | Adrian Klaver | 2026-04-29 23:37:22 | Re: Confirmation on concurrent SELECT FOR UPDATE with ON CONFLICT DO NOTHING |