Re: dropdb --force

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Cc: 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-07-07 22:07:02
Message-ID: CA+hUKGLeSocuJkR=Wny3GkUO57d92LH79deHQdb4DgiS+XcrHw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jun 27, 2019 at 7:15 AM Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
> fixed

Hi Pavel,

FYI t/050_dropdb.pl fails consistently with this patch applied:

https://travis-ci.org/postgresql-cfbot/postgresql/builds/555234838

--
Thomas Munro
https://enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2019-07-07 22:15:48 Re: Avoiding deadlock errors in CREATE INDEX CONCURRENTLY
Previous Message Thomas Munro 2019-07-07 22:02:03 Re: Ought to use heap_multi_insert() for pg_attribute/depend insertions?