| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: ReplicationSlotRelease() crashes when the instance is in the single user mode |
| Date: | 2025-02-20 02:27:11 |
| Message-ID: | CAKFQuwbnBkGZAM+5b1DWmbqU5W7b1r-nQsw87BukrUC5WLrJXg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Feb 19, 2025 at 7:23 PM Hayato Kuroda (Fujitsu) <
kuroda(dot)hayato(at)fujitsu(dot)com> wrote:
> I intentionally used elog() because I thought single user mode is not
> user-facing.
> But it is OK for me to use ereport() instead.
>
Single-user mode is also known as "Oh crap!" mode, something used when
starting the server in multi-user model fails for non-trivial reasons.
It is also what at least one PostgreSQL Online Service (a.k.a. fiddle) uses
as an implementation choice.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ajin Cherian | 2025-02-20 02:30:18 | Re: Proposal: Filter irrelevant change before reassemble transactions during logical decoding |
| Previous Message | Hayato Kuroda (Fujitsu) | 2025-02-20 02:22:41 | RE: ReplicationSlotRelease() crashes when the instance is in the single user mode |