a wrote:
> I was request to write a trigger that perform the following function:
>
> 1, The trigger will be set to exam all statement that will result change of
> datas
>
> 2, The trigger will exam three information other than the data updated or
> inserted:
>user name, password and reasons
OK no need of a new hook.
I'll try to implement what you suggest here, but this clearly exceeds my
(poor) development skill.
As you also noticed, in addition to collect this SQL statement counters for
the corresponding QueryId,
I would have been interested in its PlanId ... but it's an other subj
On 04/28/2018 10:36 AM, Jonas Pedersen wrote:
Hi list
I have recently upgraded my PostGIS 2.4.1 to 2.4.3, which introduced a
problem caused by one of the dependencies (geos 3.5.0 -> 3.6.2).
Now I would like to do a yum history undo to return my system to its
previous state, but when invoking
