| From: | Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com> |
|---|---|
| To: | surya poondla <suryapoondla4(at)gmail(dot)com> |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #19382: Server crash at __nss_database_lookup |
| Date: | 2026-07-16 06:23:39 |
| Message-ID: | CAN4CZFNqF1KOi_O1yw35UOrnpHGFWsj-tbfS5wwXOvJK+TfZkQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
> the other needs more design work than a small amendment.
I agree that one seems more difficult, I'll also think about it but so
far I don't have a better idea than what you suggested.
> I'd rather propose a design for this separately, likely a session-scoped
> set of "types altered in this transaction" plus
> a check at composite-read time. Happy to open a fresh thread on it.
That's fine with me if others agree with the approach, the current
patch is a clear improvement over the current behavior.
Case 2 is the only remaining issue I can reproduce currently, I can
crash the server with multiple variations with it, but those all
follow the same generic idea.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rafia Sabih | 2026-07-16 09:19:09 | Re: Two issues with REFRESH MATERIALIZED VIEW CONCURRENTLY |
| Previous Message | Hayato Kuroda (Fujitsu) | 2026-07-16 05:58:56 | RE: BUG #19547: libpqrcv_create_slot dereferences NULL on a malformed CREATE_REPLICATION_SLOT reply |