Re: Error: server closed the connection unexpectedly

From: Ron <ronljohnsonjr(at)gmail(dot)com>
To: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Error: server closed the connection unexpectedly
Date: 2021-10-10 21:26:07
Message-ID: e14d06d6-f997-4523-86dd-8d9654936f7d@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 10/10/21 3:12 PM, Adrian Klaver wrote:
> On 10/10/21 12:30, Ron wrote:
>> On 10/10/21 2:20 PM, Tom Lane wrote:
>>> Ron<ronljohnsonjr(at)gmail(dot)com> writes:
>>>> I think Anil mentioned that there's *nothing* in the Postgresql server
>>>> log,
>>>> even (in my case) with log_min_messages cranked to debug5.
>>> I'm skeptical that you're looking in the right place, then.
>>> What do you get from
>>>
>>> show log_destination;
>>> show log_directory;
>>
>> This is AWS RDS Postgresql.  The db server log is accessed via a web
>> interface, and is /the/ postgresql log just like you see in vanilla
>> Postgresql.
>>
>> I've attached it.  My attempt to connect happened some time between
>> between 04:10:30 and 04:17:30.
>
> Is that you sending the SIGHUP's?

Kinda.  It's the AWS version of "pg_ctl reload" after modifying dynamic
entries in the parameter group (aka postgresql.conf).

--
Angular momentum makes the world go 'round.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Ken Wang 2021-10-11 04:17:06
Previous Message Adrian Klaver 2021-10-10 20:17:23 Re: Error: server closed the connection unexpectedly