From: Tom Lane <tgl@sss.pgh.pa.us>
To: Todd Cook <cookt@blackduck.com>
Cc: David Rowley <dgrowleyml@gmail.com>
Cc: pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org>
Subject: Re: BUG #19067: On master at commit 66cdef4425f3, "psql -c 'select 1' dbname" causes the backend to seg fault
Date: Mon, 29 Sep 2025 11:55:31 -0400
Message-ID: <202543.1759161331@sss.pgh.pa.us> (raw)
In-Reply-To: <E7E4ED65-A43A-449E-B6E9-DC34BFEB1EBC@blackduck.com>
References: <19067-9a2a03ceb9a4e46c@postgresql.org>
<CAApHDvp+-DDWbTcjCafGkXeoJmOvUZ9_F2tnW2dfqdhPhrouZQ@mail.gmail.com>
<E7E4ED65-A43A-449E-B6E9-DC34BFEB1EBC@blackduck.com>
Todd Cook <cookt@blackduck.com> writes:
> On 9/27/25, 5:07 AM, "David Rowley" <dgrowleyml@gmail.com <mailto:dgrowleyml@gmail.com>> wrote:
>> I think it's more likely you need to do "make clean" before building.
> Generally, when is that needed? I pulled and built master last Monday without any problems,
> didn't touch the tree, then pulled and built again on Friday and started getting the seg faults.
> I had expected an incremental build to work in that scenario.
If you use --enable-depend that should generally work, but without
it you'd better "make clean" any time *.h files change.
regards, tom lane
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-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, cookt@blackduck.com, dgrowleyml@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #19067: On master at commit 66cdef4425f3, "psql -c 'select 1' dbname" causes the backend to seg fault
In-Reply-To: <202543.1759161331@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