=?UTF-8?B?0JDQvdGC0YPQsNC9INCS0LjQvtC70LjQvQ==?=
writes:
> I made patch for this problem, I changed event_trigger, for
> definitions of temporality
> DEFAULT VALUE
I looked over this patch. I understand what you want to fix,
and I agree with the general plan of pushing the namespace-lookup
code
> Hi everyone,
> I found one bug, when you delete temporary table with DEFAULT VALUE. The
> row about this VALUE in the pg_event_trigger_dropped_objects() contains
> “False” in the column “is_temporary”. But if you look at column “name_obj”,
> you see “for pg_temp.table_name”. So PostgreSQL know, t
Hi everyone,
I made patch for this problem
Cheers
Antoine Violin
сб, 7 дек. 2024 г. в 18:38, Антуан Виолин :
> Hi everyone,
> I found one bug, when you delete temporary table with DEFAULT VALUE. The
> row about this VALUE in the pg_event_trigger_dropped_objects() contains
> “False” in the colum
Hi everyone,
I found one bug, when you delete temporary table with DEFAULT VALUE. The
row about this VALUE in the pg_event_trigger_dropped_objects() contains
“False” in the column “is_temporary”. But if you look at column “name_obj”,
you see “for pg_temp.table_name”. So PostgreSQL know, that it is
