On Tue, 18 May 2021 at 08:42, wrote:
> Running delete from table1 where id = 48938 the trigger for constraint runs
> for 20 seconds
>
> Event when doing a simple select from table2 where table1_id = 48938 takes
> about 8 seconds
Does EXPLAIN show it uses a seq scan for this 8-second SELECT?
If
Good day
I'm struggling with a Postgres 13 performance issue and nothing I do seem to
help.
I have two tables with one having a foreign key to the other. It happens to
be for this one client the foreign key is always null, so no violation would
be possible. When deleting from the one table
