From: | Garrett Thornburg <film42(at)gmail(dot)com> |
---|---|
To: | Isaac Morland <isaac(dot)morland(at)gmail(dot)com> |
Cc: | Aleksander Alekseev <aleksander(at)timescale(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: Looking for context around which event triggers are permitted |
Date: | 2023-07-17 16:04:42 |
Message-ID: | CAEEqfk4Qyqhy7ubiiWVTmUQ8xrfgN=PzKjFSGhxdqgRckP3Rxw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
That's a good point, Isaac. Select into, security label, comment, etc are
all maintenance style commands but are already added to the matrix. I do
think there's a good case to include other maintenance related commands as
event triggers. Suppose you want to know the last time a table was vacuumed
or the last time a table was reindexed. If you can trigger off of these
maintenance commands, there's a lot you could build on top of postgres to
make the maintenance experience easier. Seems like a positive thing.
The code exists but they are disabled at the moment. Happy to enable those
with a patch if it's as Aleksander said. Meaning, no real reason they were
disabled other than someone thought folks wouldn't need them.
From | Date | Subject | |
---|---|---|---|
Next Message | Aleksander Alekseev | 2023-07-17 16:31:19 | Re: Looking for context around which event triggers are permitted |
Previous Message | Melih Mutlu | 2023-07-17 15:54:30 | Re: [PATCH] Reuse Workers and Replication Slots during Logical Replication |