| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Jeff Davis <pgsql(at)j-davis(dot)com>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: [15] Custom WAL resource managers, single user mode, and recovery |
| Date: | 2022-07-15 03:42:56 |
| Message-ID: | 3228527.1657856576@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Andres Freund <andres(at)anarazel(dot)de> writes:
> On 2022-07-14 20:48:57 -0400, Tom Lane wrote:
>> (I wonder if we shouldn't refactor this so that the postmaster
>> and standalone mode share more of the initialization logic.
>> Keeping these bits in sync seems unlikely to happen otherwise.)
> Yes, that might be worthwhile. OTOH, I wonder if we should spend that time to
> remove single user mode instead - the architectural complexity really doesn't
> seem worth it anymore, and IMO my prototype from a few months back showed that
> it's feasible.
I dunno ... if your DB is in bad enough shape that you need to resort
to single-user mode, you probably don't want any more moving parts
in the system than you absolutely have to have. Autovacuum, custom
background workers, and the like are going to be counterproductive.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2022-07-15 03:58:27 | Re: [15] Custom WAL resource managers, single user mode, and recovery |
| Previous Message | Andres Freund | 2022-07-15 03:42:18 | Re: Auto-vacuum timing out and preventing connections |