From: | Japin Li <japinli(at)hotmail(dot)com> |
---|---|
To: | Daniel Verite <daniel(at)manitou-mail(dot)org> |
Cc: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: Question about user/database-level parameters |
Date: | 2022-08-04 15:03:47 |
Message-ID: | ME3P282MB16675DE00C260765230D7887B69F9@ME3P282MB1667.AUSP282.PROD.OUTLOOK.COM |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, 04 Aug 2022 at 19:29, Daniel Verite <daniel(at)manitou-mail(dot)org> 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 local_preload_libraries, in a quick test.
>
> That is, you can log in by invoking psql with:
> PGOPTIONS="-c local_preload_libraries="
> and issue the ALTER USER to reset things back to normal
> without stopping the instance.
Oh, great! Thank you very much!
--
Regrads,
Japin Li.
ChengDu WenWu Information Technology Co.,Ltd.
From | Date | Subject | |
---|---|---|---|
Next Message | Andrey Borodin | 2022-08-04 16:18:39 | Re: Use fadvise in wal replay |
Previous Message | Daniel Gustafsson | 2022-08-04 14:32:37 | Re: [doc] fix a potential grammer mistake |