From: | Michael Paquier <michael(at)paquier(dot)xyz> |
---|---|
To: | Legs Mansion <1027644833(at)qq(dot)com> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: A Question about InvokeObjectPostAlterHook |
Date: | 2023-04-22 08:44:13 |
Message-ID: | ZEOeXUMtJ5xv5oZM@paquier.xyz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Apr 21, 2023 at 04:16:10PM +0800, Legs Mansion wrote:
> actually, some location can be tricky to add.
> it looks like CREATE, but it’s actually ALTER, should call
> InvokeObjectPostAlterHook instead
> of InvokeObjectPostCreateHook? eg.,CREATE OR REPLACE, CREATE
> TYPE(perfecting shell type)
Sure, it could be possible to plaster more of these depending on the
control one may want with OATs. Coming back to the main you point of
the thread you were making, what are the use cases with ALTER TABLE
you were interested in for sepgsql on top of what the patch I sent
upthread is doing?
Note that it is perfectly fine to do the changes incrementally, though
I'd rather add some proper coverage for each one of them using the
module I've patched (sepgsql's tests are annoying to setup and run).
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2023-04-22 08:50:22 | Re: run pgindent on a regular basis / scripted manner |
Previous Message | Michael Paquier | 2023-04-22 08:39:28 | Re: Fix documentation for max_wal_size and min_wal_size |