Re: BUG #18599: server closed the connection unexpectedly

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Karim Chaid <kchaid(at)hotmail(dot)com>
Cc: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, David Rowley <dgrowleyml(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #18599: server closed the connection unexpectedly
Date: 2024-09-07 06:22:31
Message-ID: CABUevEx8UcKn+d2up5GdrT298do=8xW87Zd_dBJFUHKsadd_VQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Sat, Sep 7, 2024, 00:18 Karim Chaid <kchaid(at)hotmail(dot)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

>

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Joe Conway 2024-09-07 14:09:47 Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
Previous Message Basha 2024-09-07 02:27:26 Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications