Re: BUG #17791: Assert on procarray.c

From: Robins Tharakan <tharakan(at)gmail(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #17791: Assert on procarray.c
Date: 2023-02-15 11:16:50
Message-ID: CAEP4nAyGSih4+zMk7-XV84rz73bNZp4tn0yFjokEYc7c=4w7-w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi,

On Wed, 15 Feb 2023 at 15:36, Andres Freund <andres(at)anarazel(dot)de> wrote:
>
> What range of versions / commits are you testing this workload on?
> Are you testing 11 as well? Because I don't see why we'd have the issue on 12,
> but not 11.

My bad, should have explained this upfront. The tests I run are *always* on
STABLE (or master). IIRC I had encountered an error in v10 / v11 and had
disabled testing those majors. Since currently, I am only testing v12+, this may
exist in previous major versions, just not visible in my testing.

> It might be worth trying to reproduce the issue with a much lower ulimit -S
> -n, to reach the problematic state more quickly. A reproducer would be very
> useful.... Those are indeed not very interesting - although it'd be interesting
> to know what caused the clients to go away.

I am travelling the coming few weeks, but would keep this in mind and revert
once I have something to share.

-
robins

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2023-02-15 12:15:53 BUG #17796: pgcrypto undecryptable blowfish data previous stored with openssl 1.1.1 with builtin decrypter one
Previous Message Dean Rasheed 2023-02-15 09:41:13 Re: BUG #17792: MERGE uses uninitialized pointer and crashes when target tuple is updated concurrently