Re: BUG #16056: Actually PGADMIN4

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: PG Bug reporting form <noreply(at)postgresql(dot)org>
Cc: PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>, paul(at)scom(dot)ca
Subject: Re: BUG #16056: Actually PGADMIN4
Date: 2019-10-14 19:53:12
Message-ID: CAKFQuwZhAL4uyKs8_sZe9whedqV33vs9NNcGQNN+JZ+H-Lw=NA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Mon, Oct 14, 2019 at 12:09 PM PG Bug reporting form <
noreply(at)postgresql(dot)org> wrote:

> The following bug has been logged on the website:
>
> Bug reference: 16056
> Logged by: Paul Kudla
> Email address: paul(at)scom(dot)ca
> PostgreSQL version: 12.0
> Operating system: windows ten
> Description:
>
> Unable to stop it from asking for a master password
>
[...]

> i lost 2 hours messing with this because you prompted me to do an update,
> and have given up thus the bug report
>
> PG Admin version is 4.13
>
> Please provide a documentated way to deal with this issue.
>

pgAdmin is a third-party application and as such has its own support
channels independent of the core PostgreSQL project.

You can find information on them here:

https://www.pgadmin.org/support/

David J.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2019-10-14 23:30:08 Re: BUG #16055: pgAdmin 4 - ERROR: operator does not exist: - oid
Previous Message Tomas Vondra 2019-10-14 16:35:38 Re: BUG #16045: vacuum_db crash and illegal memory alloc after pg_upgrade from PG11 to PG12