From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-committers <pgsql-committers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: pgsql: Fix minor problems with non-exclusive backup cleanup. |
Date: | 2020-08-06 18:56:14 |
Message-ID: | CA+TgmoaHJoYy+N5+0prqo5xuBNrQ5-KtW_Vmnm+Wgg84aC3GPg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
On Thu, Aug 6, 2020 at 2:19 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <rhaas(at)postgresql(dot)org> writes:
> > Fix minor problems with non-exclusive backup cleanup.
>
> Seems like there's an extra space in this error message in
> do_pg_abort_backup:
>
> + if (emit_warning)
> + ereport(WARNING,
> + (errmsg("aborting backup due to backend exiting before pg_stop_back up was called")));
Ah, crap. Peter fixed that before, and I forgot to include it when
back-patching.
> Also, while I'm bugging you: it wasn't quite clear from the thread
> whether this is alone sufficient to fix the user-visible issue
> reported by Bharath Rupireddy, or whether we still need to change
> the JIT logic as well to do that.
I believe it suffices, but see also the commit I pushed to master.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2020-08-06 19:05:22 | Re: pgsql: Fix minor problems with non-exclusive backup cleanup. |
Previous Message | Robert Haas | 2020-08-06 18:20:55 | pgsql: Register llvm_shutdown using on_proc_exit, not before_shmem_exit |