Re: BUG #18599: server closed the connection unexpectedly - Mailing list pgsql-bugs

From Karim Chaid
Subject Re: BUG #18599: server closed the connection unexpectedly
Date
Msg-id CY5PR10MB6023951272F6128DF1F858B3C39A2@CY5PR10MB6023.namprd10.prod.outlook.com
Whole thread Raw
In response to Re: BUG #18599: server closed the connection unexpectedly  (Magnus Hagander <magnus@hagander.net>)
List pgsql-bugs
Thank you all in helping with this issue.
Regards

From: Magnus Hagander <magnus@hagander.net>
Sent: Saturday, September 7, 2024 1:22 AM
To: Karim Chaid <kchaid@hotmail.com>
Cc: Thomas Munro <thomas.munro@gmail.com>; David Rowley <dgrowleyml@gmail.com>; PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Subject: Re: BUG #18599: server closed the connection unexpectedly
 

On Sat, Sep 7, 2024, 00:18 Karim Chaid <kchaid@hotmail.com> wrote:
One quick test recommended for me is to convert the columnar tables to heap.
Upon doing it, the query worked. It was hung in the first attempt but in the second attempt worked fine.

I would to get this resolved for columnar setup.


There's no such thing as columnar in PostgreSQL. You must be using either a fork or some pretty complex extension. It seems pretty clear that the problem is in that code and not in PostgreSQL since it goes away when you switch off it. So you're probablh better off reporting it to them. 

/Magnus 

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #18608: Assert in check_agglevels_and_constraints() fails on creating a rule with aggr(NEW) in subselect
Next
From: Thomas Munro
Date:
Subject: Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows