| From: | Noah Misch <noah(at)leadboat(dot)com> |
|---|---|
| To: | Kirill Reshke <reshkekirill(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: TerminateOtherDBBackends code comments inconsistency. |
| Date: | 2024-05-16 21:18:01 |
| Message-ID: | 20240516211801.8d.nmisch@google.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Apr 30, 2024 at 09:10:52AM +0530, Amit Kapila wrote:
> On Tue, Apr 30, 2024 at 2:58 AM Noah Misch <noah(at)leadboat(dot)com> wrote:
> > On Mon, Apr 29, 2024 at 10:18:35AM +0530, Amit Kapila wrote:
> > > 3a9b18b309 didn't change the docs of pg_terminate_backend and whatever
> > > is mentioned w.r.t permissions in the doc of that function sounds
> > > valid for drop database force to me. Do you have any specific proposal
> > > in your mind?
> >
> > Something like the attached.
>
> LGTM.
Pushed as commit 372700c. Thanks for the report and the review.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jacob Champion | 2024-05-16 21:24:20 | Re: commitfest.postgresql.org is no longer fit for purpose |
| Previous Message | Nathan Bossart | 2024-05-16 21:16:38 | optimizing pg_upgrade's once-in-each-database steps |