| From: | PG Doc comments form <noreply(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-docs(at)lists(dot)postgresql(dot)org |
| Cc: | james(at)yobota(dot)xyz |
| Subject: | Transaction Management |
| Date: | 2020-07-07 10:46:59 |
| Message-ID: | 159411881905.2097.9642551635962048513@wrigleys.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/12/plpgsql-transactions.html
Description:
Hello,
We are looking to use transaction management and have run into a limitation
when the procedure is security definer. There doesn't appear to be any
reference to this in the
https://www.postgresql.org/docs/13/plpgsql-transactions.html so we cannot
see when the limitation is lifted.
Are you able to clarify the situation with this between PG11, 12 and 13? We
are hoping the limitation is lifted as we cannot see what the reason for the
limitation is.
Thanks,
James
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Rowley | 2020-07-07 12:54:44 | Re: Default setting for enable_hashagg_disk (hash_mem) |
| Previous Message | Amit Kapila | 2020-07-07 09:50:26 | Re: Default setting for enable_hashagg_disk (hash_mem) |