| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | peregrammist02(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #17797: connection error |
| Date: | 2023-02-16 19:31:08 |
| Message-ID: | CAKFQuwaTZkV62u6hBekQSLNV2sfyaAgCXiKCvzfk+WUcF0p9Ag@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Thu, Feb 16, 2023 at 12:24 PM PG Bug reporting form <
noreply(at)postgresql(dot)org> wrote:
> The following bug has been logged on the website:
>
> Bug reference: 17797
> Logged by: ? ?
> Email address: peregrammist02(at)gmail(dot)com
> PostgreSQL version: 15.2
> Operating system: windows 10(64bit)
> Description:
>
> i cant connect to the database even though i entered the correct
> data(host='localhost', port='5432')
>
This is not a bug so this list/form is not the correct place to ask for
help. Such requests should be directed to the -novice or -general list.
Your failure to include the exact error message you are getting is also a
problem you should correct when you ask this question in a more appropriate
forum. Likewise for actually explaining what software you are connecting
with.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2023-02-17 10:00:00 | BUG #17798: Incorrect memory access occurs when using BEFORE ROW UPDATE trigger |
| Previous Message | Alex Richman | 2023-02-16 19:08:14 | Re: Logical Replica ReorderBuffer Size Accounting Issues |