Greg wrote:
> is "DROP TRIGGER" transaction safe?... I mean, could I do:
>
> BEGIN
> DROP TRIGGER category_mv_ut;
> ... insert rows
> ... update materialized view table
> CREATE TRIGGER category_mv_ut AFTER UPDATE ON items
> FOR EACH ROW EXECUTE PROCEDURE update_ut();
> COMMIT;
>
> .. without other sessions being affected?
This is exactly what I do to avoid matview bulk-update performance issues.
--Phil.