Re: Two round for Client Authentication

2018-06-14 Thread Yinjie Lin
Many thanks to Marko and David for your reply. It really helped. Now I am playing with extension auth_delay, which uses ClientAuthentication_hook. But I find it not easy to distinguish the first connection of psql from the second one with empty password, since the variable 'status' are both STATUS

Re: Two round for Client Authentication

2018-06-13 Thread David G. Johnston
On Wednesday, June 13, 2018, Yinjie Lin wrote: > > Why are there two such progresses forked? I think one round should be > enough, like when using pgAdmin. > You can use the --password option to prevent it. """ This option is never essential, since psql will automatically prompt for a password i

Re: Two round for Client Authentication

2018-06-13 Thread Marko Tiikkaja
On Thu, Jun 14, 2018 at 7:12 AM, Yinjie Lin wrote: > Currently I am reading and testing code about Client Authentication, but I > find that there are two progresses forked if I login using psql, while only > one progress is forked if using pgAdmin. > If psql finds the server asks for a password,