From: | "Bossart, Nathan" <bossartn(at)amazon(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Improving psql's \password command |
Date: | 2021-11-19 23:03:26 |
Message-ID: | 9D3BFA94-DEF2-4B43-B240-8ADC595ECA7A@amazon.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 11/19/21, 9:17 AM, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "Bossart, Nathan" <bossartn(at)amazon(dot)com> writes:
>> Okay, here is an attempt at adding control-C support for \prompt and
>> \connect. It was reasonably straightforward. I did have to teach
>> simple_prompt_extended() to add a newline after a cancellation when
>> "echo" is true.
>
> LGTM, pushed after very minor fooling with the comments.
Thanks!
>> I think that's it for psql. After a quick glance, I didn't see any
>> other obvious candidates for control-C support, but I'll look a little
>> closer to be sure.
>
> Hmm, initdb's prompt-for-superuser-password might need it.
> I think the rest of our frontend programs don't trap SIGINT,
> or at least don't do so while requesting user input.
I'm able to cancel the superuser password prompt in initdb already.
It looks like the signal handlers aren't set up until after
get_su_pwd(). I did find some missing control-C handling in
pg_receivewal/pg_recvlogical, though. Attached is a patch for those.
Nathan
Attachment | Content-Type | Size |
---|---|---|
v1-0001-Add-control-C-handling-for-password-prompts-in-pg.patch | application/octet-stream | 6.0 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Bossart, Nathan | 2021-11-19 23:45:40 | Re: Should rename "startup process" to something else? |
Previous Message | Andres Freund | 2021-11-19 23:02:04 | Re: Adding CI to our tree |