| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Rahila Syed <rahilasyed90(at)gmail(dot)com>, Daniel Gustafsson <daniel(at)yesql(dot)se>, torikoshia <torikoshia(at)oss(dot)nttdata(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Enhancing Memory Context Statistics Reporting |
| Date: | 2026-01-13 21:11:24 |
| Message-ID: | CA+TgmoZLJoXs-ZwuPQtYVpnt+JtiBZdM+K72mRutnTAzTssYdQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jan 13, 2026 at 3:26 PM Andres Freund <andres(at)anarazel(dot)de> wrote:
> All the error handling paths (hopefully) have an LWLockReleaseAll()... Which
> is pretty crucial given that we do stuff outside of transactions in other
> places.
>
> That doesn't mean the other concerns about resource management are unfounded,
> however.
Yeah, I actually wasn't completely sure about that particular comment.
I think what will happen if we ERROR outside of a transaction is that
it will become FATAL and kill the backend, but I'm not 100% positive
about that.
--
Robert Haas
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2026-01-13 21:14:09 | Re: [PATCH] Add permit_unlogged_tables GUC to control unlogged table creation. |
| Previous Message | harinath kanchu | 2026-01-13 20:47:48 | [PATCH] Add permit_unlogged_tables GUC to control unlogged table creation. |