| From: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
|---|---|
| To: | Sami Imseih <samimseih(at)gmail(dot)com> |
| Cc: | Alexander Lakhin <exclusion(at)gmail(dot)com>, Rahila Syed <rahilasyed90(at)gmail(dot)com>, Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Improve LWLock tranche name visibility across backends |
| Date: | 2025-11-11 19:28:08 |
| Message-ID: | aROOSLQwamg339K-@nathan |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Nov 10, 2025 at 05:17:47PM -0600, Sami Imseih wrote:
> Maybe we can improve the error message by showing
> the "name", like this, In case, there are nested calls.
>
> ```
> else if (!entry->initialized)
> {
> ereport(ERROR,
> (errmsg("requested DSM segment \"%s\" failed initialization", name)));
> }
> ```
Done.
--
nathan
| Attachment | Content-Type | Size |
|---|---|---|
| v3-0001-DSM-registry-ERROR-if-entry-was-not-initialized.patch | text/plain | 3.6 KB |
| v3-0002-test_dsa-Avoid-leaking-LWLock-tranches.patch | text/plain | 2.0 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Treat | 2025-11-11 19:43:19 | Re: another autovacuum scheduling thread |
| Previous Message | Bryan Green | 2025-11-11 19:22:49 | Re: [Patch] Windows relation extension failure at 2GB and 4GB |