Re: BUG #19067: On master at commit 66cdef4425f3, "psql -c 'select 1' dbname" causes the backend to seg fault

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Todd Cook <cookt(at)blackduck(dot)com>
Cc: David Rowley <dgrowleyml(at)gmail(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #19067: On master at commit 66cdef4425f3, "psql -c 'select 1' dbname" causes the backend to seg fault
Date: 2025-09-29 15:55:31
Message-ID: 202543.1759161331@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Todd Cook <cookt(at)blackduck(dot)com> writes:
> On 9/27/25, 5:07 AM, "David Rowley" <dgrowleyml(at)gmail(dot)com <mailto:dgrowleyml(at)gmail(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2025-09-29 17:34:33 Re: Cast to regrole on a literal string in a PL/pgSQL function
Previous Message Todd Cook 2025-09-29 15:28:13 Re: BUG #19067: On master at commit 66cdef4425f3, "psql -c 'select 1' dbname" causes the backend to seg fault