| From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
|---|---|
| To: | "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Validate SERVER subscription conninfo during ALTER SUBSCRIPTION ... OWNER TO |
| Date: | 2026-07-22 00:40:10 |
| Message-ID: | CAHGQGwHMg1j+1+t7hNi7YnCAMFnaw7MH1TjGodCQj8pZcen2Yw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jul 21, 2026 at 6:45 PM Hayato Kuroda (Fujitsu)
<kuroda(dot)hayato(at)fujitsu(dot)com> wrote:
> Not sure, but can we also meet the similar situation via ALTER USER MAPPING
> ... (DROP password) command? I.e., the command would succeed but the worker
> will fail.
> If so, should we also fix the case? Or it's something like "Don't do that" situation?
Yes, a similar situation can probably be created also by changing
the underlying user mapping.
But, I think that's part of a broader dependency invalidation problem.
Similar issues could also arise from commands such as DROP USER MAPPING,
ALTER SERVER, and ALTER FOREIGN DATA WRAPPER ... CONNECTION/NO CONNECTION.
If we decide to address the ALTER USER MAPPING case, we should probably
consider those related cases as well. Since that's a broader topic, I think
it's better to discuss that separately.
Regards,
--
Fujii Masao
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2026-07-22 00:56:03 | Re: Unexpected behavior after OOM errors |
| Previous Message | Fujii Masao | 2026-07-22 00:33:51 | Re: Validate SERVER subscription conninfo during ALTER SUBSCRIPTION ... OWNER TO |