| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Andrii <andriikrivich(at)gmail(dot)com> |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Bug Report: PostgreSQL 16 crashes on ALTER USER CURRENT_USER WITH PASSWORD |
| Date: | 2026-01-07 16:32:14 |
| Message-ID: | s7u54xhth5lxg5vticfj75bstge4amradtnigbqefcfqqhrzwp@shidj6abnxbf |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
hi,
On 2026-01-06 14:58:52 +0100, Andrii wrote:
> PostgreSQL server crashes with a segmentation fault when executing ALTER
> USER CURRENT_USER WITH PASSWORD in PostgreSQL 16.10 and 16.11. The crash
> results in immediate termination of the backend process and forces a full
> instance restart.
> Steps to Reproduce
>
> 1.
>
> Connect to PostgreSQL as a regular role (non-superuser):
>
> psql -U test_user -d testdb
>
> 2.
>
> Execute the following command:
>
> ALTER USER CURRENT_USER WITH PASSWORD 'new_password';
I can't reproduce that. Is it possible that you have some extensions loaded
that that are hooking into the command? What is your shared_preload_libraries
set to?
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Srinath Reddy Sadipiralla | 2026-01-07 16:33:17 | Re: Bug Report: PostgreSQL 16 crashes on ALTER USER CURRENT_USER WITH PASSWORD |
| Previous Message | Dean Rasheed | 2026-01-07 12:52:25 | Re: BUG #19355: Attempt to insert data unexpectedly during concurrent update |