| 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>, jude(dot)cardeno(at)wipro(dot)com |
| Subject: | Re: BUG #16044: Could not send data to server |
| Date: | 2019-10-08 16:36:57 |
| Message-ID: | CAKFQuwaJ4VPBM_r4-H1wFzPnaW5bZoJnneMrP16ouOVoYGkdjQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Tue, Oct 8, 2019 at 3:08 AM PG Bug reporting form <noreply(at)postgresql(dot)org>
wrote:
> The following bug has been logged on the website:
>
> Bug reference: 16044
> Logged by: Jude Cardeño
> Email address: jude(dot)cardeno(at)wipro(dot)com
> PostgreSQL version: Unsupported/Unknown
> Operating system: Windows
> Description:
>
> Hi PGSupport,
>
This doesn't seem like a bug, in core PostgreSQL (which this list is for)
or PGAdmin (which this list isn't for - that application has their own
support channel). You should file this help ticket with whichever
company/person setup the described network and applications.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2019-10-08 17:08:53 | BUG #16045: vacuum_db crash and illegal memory alloc after pg_upgrade from PG11 to PG12 |
| Previous Message | Andres Freund | 2019-10-08 16:09:53 | Re: BUG #16039: PANIC when activating replication slots in Postgres 12.0 64bit under Windows |