| From: | thehesiod <thehesiod(at)gmail(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: overriding current_timestamp |
| Date: | 2020-11-05 00:39:55 |
| Message-ID: | 1604536795380-0.post@n3.nabble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-11-05 00:43:51 | array_cat anycompatible change is breaking xversion upgrade tests |
| Previous Message | Michael Paquier | 2020-11-05 00:16:10 | Re: "unix_socket_directories" should be GUC_LIST_INPUT? |