From: | Japin Li <japinli(at)hotmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
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-02 05:59:39 |
Message-ID: | MEYP282MB1669FBBE8BE8AA9EC4ECD7E1B69D9@MEYP282MB1669.AUSP282.PROD.OUTLOOK.COM |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, 02 Aug 2022 at 13:44, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Japin Li <japinli(at)hotmail(dot)com> 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 impossible for a superuser to shoot himself in the foot.
>
> Test your settings more carefully before applying them to a
> production database that you can't afford to mess up.
>
Thanks for your explanation! Got it.
--
Regrads,
Japin Li.
ChengDu WenWu Information Technology Co.,Ltd.
From | Date | Subject | |
---|---|---|---|
Next Message | Nikita Malakhov | 2022-08-02 06:15:12 | Re: Pluggable toaster |
Previous Message | John Naylor | 2022-08-02 05:52:53 | Re: fix typos |