Postgresql : pg_temp & pg_toast_temp

Vishwanath Kummera <kvishu83@gmail.com> writes:

I am seeing there are many schemas created, this is specially when
enabled "CONCURRENTLY" option for refreshing materialized views through
table trigger.

pg_temp_1... pg_temp_30
pg_toast_temp_1... pg_toast_temp_30

Yes, that's by design. There's a separate temp schema for each backend
session "slot", which gets created when first needed.

If this is by design the temp schemas get created with the "CONCURRENTLY"
option, is there any way to clean-up them automatically?

No. It'd just lead to thrashing/bloat in the pg_namespace catalog,
since they'd be needed again eventually.

regards, tom lane