Re: dropdb --force

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: vignesh C <vignesh21(at)gmail(dot)com>
Cc: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Dilip Kumar <dilipbalaut(at)gmail(dot)com>, Ryan Lambert <ryan(at)rustprooflabs(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Anthony Nowocien <anowocien(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Filip Rembiałkowski <filip(dot)rembialkowski(at)gmail(dot)com>
Subject: Re: dropdb --force
Date: 2019-09-26 14:36:36
Message-ID: CAFj8pRDCanmo4Vxoyr5sdSFS8PfwHQTc41neRaYS61zPD2k8tA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

út 24. 9. 2019 v 17:51 odesílatel vignesh C <vignesh21(at)gmail(dot)com> napsal:

> On Tue, Sep 24, 2019 at 6:22 PM Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
> wrote:
> >
> > On Sat, Sep 21, 2019 at 10:09 PM Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
> wrote:
> > >
> > > Thank you for check. I am sending updated patch
> > >
> >
> Session termination in case of drop database is solved.
> Some typos:
> + /*
> + * Similar code to pg_terminate_backend, but we check rigts first
> + * here, and only when we have all necessary rights we start to
> + * terminate other clients. In this case we should not to raise
> + * some warnings - like "PID %d is not a PostgreSQL server process",
> + * because for this purpose - already finished session is not
> + * problem.
> + */
> "rigts" should be "rights/privilege"
> "should not to raise" could be "should not raise"
>

fixed

> Regards,
> Vignesh
> EnterpriseDB: http://www.enterprisedb.com
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2019-09-26 14:38:44 Re: JSONPATH documentation
Previous Message Mike Palmiotto 2019-09-26 14:11:04 Re: Auxiliary Processes and MyAuxProc