On Thu, 04 Aug 2022 at 19:29, Daniel Verite wrote:
> Japin Li wrote:
>
>> However, if the database is in production, we cannot go into single-user
>> mode, should we provide an option to change this behavior on the fly?
>
> It already exists, through PGOPTIONS, which appears to work
> for
Japin Li wrote:
> However, if the database is in production, we cannot go into single-user
> mode, should we provide an option to change this behavior on the fly?
It already exists, through PGOPTIONS, which appears to work
for local_preload_libraries, in a quick test.
That is, you can lo
On Tue, 02 Aug 2022 at 13:44, Tom Lane wrote:
> Japin Li writes:
>> Yeah, the single-user mode works. Thank you very much!
>> However, if the database is in production, we cannot go into single-user
>> mode,
>> should we provide an option to change this behavior on the fly?
>
> There is not,
Japin Li writes:
> Yeah, the single-user mode works. Thank you very much!
> However, if the database is in production, we cannot go into single-user mode,
> should we provide an option to change this behavior on the fly?
There is not, and never will be, a version of Postgres in which
it's imposs
On Tue, 02 Aug 2022 at 13:01, Kyotaro Horiguchi wrote:
> At Mon, 01 Aug 2022 18:24:33 +0800, Japin Li wrote in
>>
>> Hi, hackers
>>
>> When I try to modify the parameters for all users in the following command
>> [1]
>> (the library doesn't exist), and I quit the connection, I cannot log in
At Mon, 01 Aug 2022 18:24:33 +0800, Japin Li wrote in
>
> Hi, hackers
>
> When I try to modify the parameters for all users in the following command [1]
> (the library doesn't exist), and I quit the connection, I cannot log in the
> database, how can I bypass this checking?
>
> I find those pa
