From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
---|---|
To: | Amit Kapila <akapila(at)postgresql(dot)org> |
Cc: | pgsql-committers(at)lists(dot)postgresql(dot)org |
Subject: | Re: pgsql: Add tests for '-f' option in dropdb utility. |
Date: | 2019-11-28 13:29:48 |
Message-ID: | CAA4eK1KO6Ed1+ijUKw3M-KQc6AJZd-3Wkq7zAQA-7T08qBnrTg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
On Thu, Nov 28, 2019 at 11:49 AM Amit Kapila <akapila(at)postgresql(dot)org> wrote:
>
> Add tests for '-f' option in dropdb utility.
>
drongo doesn't seem to like this commit [1]. Below is shown in failure report:
# aborting wait: program died
# stream contents: >>psql:<stdin>:4: server closed the connection unexpectedly
# This probably means the server terminated abnormally
# before or while processing the request.
# psql:<stdin>:4: fatal: connection to server was lost
# <<
# pattern searched for: (?^m:FATAL: terminating connection due to
administrator command)
It seems to indicate that the message is not matched after we have
forcefully terminated it by Drop Database .. (force);. The first
thought that came to mind is that it is specific to this system as
this passes on other machines. It is possible that it is
Windows-specific. I'll investigate it further.
[1] - https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=drongo&dt=2019-11-28%2009%3A57%3A30
--
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Kapila | 2019-11-28 13:49:48 | Re: pgsql: Add tests for '-f' option in dropdb utility. |
Previous Message | Amit Kapila | 2019-11-28 06:18:55 | pgsql: Add tests for '-f' option in dropdb utility. |