Re: server closed the connection unexpectedly - bug report

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Jiří Ledvinka <ledvinkaj(at)sci(dot)muni(dot)cz>
Cc: "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: server closed the connection unexpectedly - bug report
Date: 2022-06-25 21:22:41
Message-ID: CAKFQuwajrdD53dMwnFsh2vePpzsx1wvsXKDnoZGFqN1P_j-LZQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Sat, Jun 25, 2022 at 2:11 PM David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> wrote:

> On Saturday, June 25, 2022, Jiří Ledvinka <ledvinkaj(at)sci(dot)muni(dot)cz> wrote:
>
>> Hello everyone. I have problem with opening DB in pgAdmin. But the DB
>> works normally. See Screenshots and logs.
>>
>> After update from version 11.10 to 11.16 it didn’t help. pgAdmin also the
>> newest, and other version work either. I cant upgrade to higher version
>> because the SW using this DB isn’t compatible with higher version. Do you
>> thing the solution is to make dump, remove the DB and import DB from the
>> dump.SQL? But there is also TimeScaleDB addon.
>>
>>
> Check logs and try just using psql to connect.
>
>
So what was process 12228? Any log messages related to it? Last server up
was 5 minutes before the logs you are showing here.

If indeed it is an attempt by pgAdmin to connect and issue that set of SQL
commands causing an access violation does the same violation occur if you
emulate it but using psql?

David J.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Dave Cramer 2022-06-25 23:15:14 Re: BUG #17518: Getting Error "new multixact has more than one updating member" when trying to delete records.
Previous Message David G. Johnston 2022-06-25 21:11:08 Re: server closed the connection unexpectedly - bug report