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>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Dilip Kumar <dilipbalaut(at)gmail(dot)com>, Ryan Lambert <ryan(at)rustprooflabs(dot)com>, 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-11-16 07:54:39 |
Message-ID: | CAFj8pRCQjzi9VHAe9zCv2XJY=fe+U6nyzqZjH=a-67GJ=fi6Jw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
so 16. 11. 2019 v 1:10 odesílatel vignesh C <vignesh21(at)gmail(dot)com> napsal:
> On Fri, Nov 15, 2019 at 1:23 PM Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
> wrote:
> >
> > updated patch attached
> >
>
> Thanks Pavel for providing updated version.
> Few comments:
> I felt the help text seems incomplete:
> @@ -159,6 +167,7 @@ help(const char *progname)
> printf(_("\nOptions:\n"));
> printf(_(" -e, --echo show the commands being
> sent to the server\n"));
> printf(_(" -i, --interactive prompt before deleting
> anything\n"));
> + printf(_(" -f, --force try to terminate other
> connection before\n"));
> printf(_(" -V, --version output version information,
> then exit\n"));
> we can change to:
> printf(_(" -f, --force try to terminate other
> connection before dropping\n"));
>
>
done. maybe alternative can be "first try to terminate other connections".
It is shorter. The current text has 78 chars, what should be acceptable
> We can add one test including -e option which validates the command
> generation including WITH (FORCE):
> +$node->safe_psql('postgres', 'CREATE DATABASE foobar2');
> +$node->issues_sql_like(
> + [ 'dropdb', '--force', 'foobar2' ],
> + qr/statement: DROP DATABASE foobar2 WITH \(FORCE\);/,
> + 'SQL DROP DATABASE (FORCE) run');
> +
>
I don't understand to this point. It is effectively same like existing test
> Also should we include one test where one session is connected to db
> and another session tries dropping with -f option?
>
I afraid so test API doesn't allow asynchronous operations. Do you have any
idea, how to it?
Regards
Pavel
>
> Regards,
> Vignesh
> EnterpriseDB: http://www.enterprisedb.com
>
Attachment | Content-Type | Size |
---|---|---|
dropdb-f-20191116.patch | text/x-patch | 4.1 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | parveen mehta | 2019-11-16 11:31:35 | Postgres on IBM z/OS 2.2.0 and 2.3.0 |
Previous Message | Michael Paquier | 2019-11-16 06:24:32 | Re: SKIP_LOCKED test causes random buildfarm failures |