Re: overriding current_timestamp - Mailing list pgsql-hackers

From thehesiod
Subject Re: overriding current_timestamp
Date
Msg-id 1604536795380-0.post@n3.nabble.com
Whole thread Raw
In response to Re: overriding current_timestamp  ("David E. Wheeler" <david@justatheory.com>)
List pgsql-hackers
so I used this method here: 
https://gist.github.com/thehesiod/d0314d599c721216f075375c667e2d9a
<https://gist.github.com/thehesiod/d0314d599c721216f075375c667e2d9a>   and
indeed does not work for current_timestamp and the like functions, and
there's another major problems, it doesn't seem to work for existing
triggers either, it seems like functions referenced by triggers are bound
when the function is created :(. I created an account to post this tid-bit
for others trying to achieve the same



--
Sent from: https://www.postgresql-archive.org/PostgreSQL-hackers-f1928748.html



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: "unix_socket_directories" should be GUC_LIST_INPUT?
Next
From: Tom Lane
Date:
Subject: array_cat anycompatible change is breaking xversion upgrade tests