Re: BF animal malleefowl reported an failure in 001_password.pl
От
Tom Lane
Тема
Re: BF animal malleefowl reported an failure in 001_password.pl
Дата
Msg-id
1801.1674159360@sss.pgh.pa.us
Ответ на
Список
Дерево обсуждения
BF animal malleefowl reported an failure in 001_password.pl "houzj.fnst@fujitsu.com" <houzj.fnst@fujitsu.com>
Re: BF animal malleefowl reported an failure in 001_password.pl Tom Lane <tgl@sss.pgh.pa.us>
Re: BF animal malleefowl reported an failure in 001_password.pl Thomas Munro <thomas.munro@gmail.com>
Re: BF animal malleefowl reported an failure in 001_password.pl Thomas Munro <thomas.munro@gmail.com>
Re: BF animal malleefowl reported an failure in 001_password.pl Thomas Munro <thomas.munro@gmail.com>
Re: BF animal malleefowl reported an failure in 001_password.pl Thomas Munro <thomas.munro@gmail.com>
Re: BF animal malleefowl reported an failure in 001_password.pl Tom Lane <tgl@sss.pgh.pa.us>
Re: BF animal malleefowl reported an failure in 001_password.pl Thomas Munro <thomas.munro@gmail.com>
Thomas Munro writes: > So I think we probably need something like the attached, which I was > originally trying to avoid. Yeah, something like that. I also wonder if you don't need to think a bit harder about the ordering of the flag checks, in particular it seems like servicing reload_request before child_exit might be a good idea (remembering that child_exit might cause launching of new children, so we want to be up to speed on relevant settings). regards, tom lane
В списке pgsql-hackers по дате отправления