| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Dominique Devienne <ddevienne(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Paul van der Linden <paul(dot)doskabouter(at)gmail(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Cannot find hstore operator |
| Date: | 2022-01-24 14:48:14 |
| Message-ID: | CAKFQuwbu7bHQq4ye0NenATY=gUG5AHaL2RDHQZ4h65Ssbn4tLQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Monday, January 24, 2022, Dominique Devienne <ddevienne(at)gmail(dot)com> wrote:
>
> After re-reading
> https://www.postgresql.org/docs/14/sql-createfunction.html in light of
> Tom's answer,
> does that mean that our `SET search_path TO {0}, 'pg_temp'`
> workaround, in the trigger below,
> to not depend on the search_path at runtime:
>
>
The general trigger documentation is kind enough to point out that the sql
language cannot be used to write trigger functions.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Dearman | 2022-01-24 14:55:21 | tstzrange on large table gives poor estimate of expected rows |
| Previous Message | Umair Shahid | 2022-01-24 12:32:55 | Proposed German Translation of Code of Conduct Policy |