Thread

1. Re: BUG #18599: server closed the connection unexpectedly

   Karim Chaid <kchaid@hotmail.com> — 2024-09-06T02:31:44Z

   This is a VM based on IBM hardware.
   I can dig into the HW side if needed.
   I will  check on jit setting and see if the issue can be resolved.
   As for the stack trace, there is no coredump and the search i did, look ile the pg_backtrace may be the way to go. I have downloaded the sourxe code from GitHub but looking for the make command options for rhel8.9 and any dependencies.
   Regards
   
   Sent from my iPhone
   
   > On Sep 4, 2024, at 4:10 PM, Thomas Munro <thomas.munro@gmail.com> wrote:
   > 
   > On Wed, Sep 4, 2024 at 5:05 PM David Rowley <dgrowleyml@gmail.com> wrote:
   >> Ideally, if you could use that to get a stack trace include that here.
   >> Alternatively, an even better option would be a self-contained series
   >> of SQL statements that we can run and recreate the issue.
   > 
   > If this is an ARM CPU (like AWS Graviton), and if setting "jit=off"
   > fixes it, then it could be the known LLVM relocation issue[1], for
   > which we have a candidate solution pending.  I mention this wild guess
   > because we're seeing a lot of these reports and it'd be much easier to
   > check that than figure out stack traces etc.
   > 
   > [1] https://www.postgresql.org/message-id/flat/CAO6_Xqr63qj%3DSx7HY6ZiiQ6R_JbX%2B-p6sTPwDYwTWZjUmjsYBg%40mail.gmail.com
   

2. Re: BUG #18599: server closed the connection unexpectedly

   Karim Chaid <kchaid@hotmail.com> — 2024-09-06T22:18:06Z

   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.
   
   Regards
   
   Sent from my iPhone
   
   > On Sep 5, 2024, at 9:31 PM, Karim Chaid <kchaid@hotmail.com> wrote:
   > 
   > This is a VM based on IBM hardware.
   > I can dig into the HW side if needed.
   > I will  check on jit setting and see if the issue can be resolved.
   > As for the stack trace, there is no coredump and the search i did, look ile the pg_backtrace may be the way to go. I have downloaded the sourxe code from GitHub but looking for the make command options for rhel8.9 and any dependencies.
   > Regards
   > 
   > Sent from my iPhone
   > 
   >>> On Sep 4, 2024, at 4:10 PM, Thomas Munro <thomas.munro@gmail.com> wrote:
   >>> 
   >>> On Wed, Sep 4, 2024 at 5:05 PM David Rowley <dgrowleyml@gmail.com> wrote:
   >>> Ideally, if you could use that to get a stack trace include that here.
   >>> Alternatively, an even better option would be a self-contained series
   >>> of SQL statements that we can run and recreate the issue.
   >> 
   >> If this is an ARM CPU (like AWS Graviton), and if setting "jit=off"
   >> fixes it, then it could be the known LLVM relocation issue[1], for
   >> which we have a candidate solution pending.  I mention this wild guess
   >> because we're seeing a lot of these reports and it'd be much easier to
   >> check that than figure out stack traces etc.
   >> 
   >> [1] https://www.postgresql.org/message-id/flat/CAO6_Xqr63qj%3DSx7HY6ZiiQ6R_JbX%2B-p6sTPwDYwTWZjUmjsYBg%40mail.gmail.com
   

3. Re: BUG #18599: server closed the connection unexpectedly

   Magnus Hagander <magnus@hagander.net> — 2024-09-07T06:22:31Z

   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
   
   >
   

4. Re: BUG #18599: server closed the connection unexpectedly

   Karim Chaid <kchaid@hotmail.com> — 2024-09-10T19:29:20Z

   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<mailto: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