|From:||Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>|
|To:||Nicolas CHAHWEKILIAN <leptitstagiaire(at)gmail(dot)com>|
|Cc:||pgsql-hackers(at)lists(dot)postgresql(dot)org, Gilles Darold <gilles(at)darold(dot)net>|
|Subject:||Re: [PATCH] Hooks at XactCommand level|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
Nicolas CHAHWEKILIAN <leptitstagiaire(at)gmail(dot)com> writes:
> As far as I am concerned, I am totally awaiting for this kind of feature
> exposed here, for one single reason at this time : the extension
> pg_statement_rollback will be much more valuable with the ability of
> processing "rollback to savepoint" without the need for explicit
> instruction from client side (and this patch is giving this option).
What exactly do these hooks do that isn't done as well or better
by the RegisterXactCallback and RegisterSubXactCallback mechanisms?
Perhaps we need to define some additional event types for those?
Or pass more data to the callback functions?
I quite dislike inventing a hook that's defined as "run during
start_xact_command", because there is basically nothing that's
not ad-hoc about that function: it's internal to postgres.c
and both its responsibilities and its call sites have changed
over time. I think anyone hooking into that will be displeased
by the stability of their results.
BTW, per the cfbot the patch doesn't even apply right now.
regards, tom lane
|Next Message||Fabien COELHO||2021-07-01 16:51:20||Re: rand48 replacement|
|Previous Message||Tom Lane||2021-07-01 16:39:39||Re: Allow batched insert during cross-partition updates|