pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed

From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
Cc: pgsql-hackers@postgresql.org
Subject: Re: ubsan
Date: Wed, 23 Mar 2022 19:02:30 -0400
Message-ID: <2886973.1648076550@sss.pgh.pa.us> (raw)
In-Reply-To: <20220323225528.hqt66d6mpx66hoal@alap3.anarazel.de>
References: <20220323173537.ll7klrglnp4gn2um@alap3.anarazel.de>
	<2771659.1648058090@sss.pgh.pa.us>
	<20220323182137.hgq4qz57yldtbhwl@alap3.anarazel.de>
	<20220323192241.tzeo6cu6mvepok53@alap3.anarazel.de>
	<2784183.1648065489@sss.pgh.pa.us>
	<20220323201234.nyh2uzot3t6becr5@alap3.anarazel.de>
	<20220323225528.hqt66d6mpx66hoal@alap3.anarazel.de>

Andres Freund <andres@anarazel.de> writes:
> Running with asan found an existing use-after-free bug in pg_waldump (*), a bug in
> dshash_seq_next() next that probably can't be hit in HEAD and a bug in my
> shared memory stats patch. I count that as a success.

Nice!

			regards, tom lane

view thread (18+ messages)  latest in thread

Message-ID: <2886973.1648076550@sss.pgh.pa.us>
Permalink:  ../2886973.1648076550@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/2886973.1648076550@sss.pgh.pa.us

copy link · copy postgr.es

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: tgl@sss.pgh.pa.us, andres@anarazel.de
  Subject: Re: ubsan
  In-Reply-To: <2886973.1648076550@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox