Date: Mon, 3 Oct 2022 14:34:19 -0500
From: Jaime Casanova <jcasanov@systemguards.com.ec>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Avoid improbable PANIC during heap_update.
Message-ID: <Yzs5O3o3QQURRv5B@ahch-to>
References: <E1lWLjP-00006Y-Ml@gemulon.postgresql.org>
 <YzVPfCKNrmi0aLEh@ahch-to>
 <YzdVJnQocQ6RHKxk@ahch-to>
 <686609.1664571080@sss.pgh.pa.us>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <686609.1664571080@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/Yzs5O3o3QQURRv5B%40ahch-to>
Precedence: bulk

On Fri, Sep 30, 2022 at 04:51:20PM -0400, Tom Lane wrote:
> Jaime Casanova <jcasanov@systemguards.com.ec> writes:
> > Just to confirm I saw this on RC1
> 
> What test case are you using?
> 

Hi,

Currently the way I have to reproduce it is:

- install the regression database
- drop all tables but: 
	hash_i4_heap, hash_name_heap, hash_txt_heap,
  	quad_poly_tbl, road
- run 10 sqlsmith processes... normally in an hour or less the problem
  appears

I have the logs from the last time it happened so maybe I can trace the
exact pattern to reproducite at will... at least to keep a test
somewhere.

BTW, so far so good with your last fix (about 12 hours now)...

-- 
Jaime Casanova
Director de Servicios Profesionales
SystemGuards - Consultores de PostgreSQL