From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andrew Dunstan <andrew@dunslane.net>
cc: Andres Freund <andres@anarazel.de>, Tomas Vondra <tomas@vondra.me>,
        Jakub Wartak <jakub.wartak@enterprisedb.com>,
        Robert Haas <robertmhaas@gmail.com>,
        PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: scalability bottlenecks with (many) partitions (and more)
In-reply-to: <947e4acd-94b9-4990-83f5-874c71d69b17@dunslane.net>
References: <7c1eeafb-2375-4ff6-8469-0640d52d44ed@vondra.me> <ffiwtzc6vedo6wb4gbwelon5nefqg675t5c7an2ta7pcz646cg@qwmkdb3l4ett> <bfca1010-e5f1-4e36-a461-61b6aad60c47@vondra.me> <5xahykogf2sg3ofdqk2li7xx3t2vh23m42jnvfwxoi5fhh7iya@girlhoxdxjzc> <486baeb2-2adc-48d2-ba9d-13c4ae43301c@vondra.me> <vgtms7b5egxdypmknxpobocqton3puhprk3ahhk45rcx4uyl33@6uetxejsc75r> <733e72fa-5fc2-48fc-ab1f-1d8f1ab387c3@vondra.me> <d5499660-1541-4749-aff4-6be88be76d99@vondra.me> <nubyc3twqd7mtuyc2rbbt2yazjzbat6mlpfgxtb2ppv2egci3g@uvptf7xmh46m> <193453.1741123834@sss.pgh.pa.us> <qdvrgej743lcddjnb4lzyakt3f5bs2oz34r274wbmgc2g4474q@utqqrqiih65h> <197167.1741125678@sss.pgh.pa.us> <8a1a5c10-0644-4ea0-a9e8-73d3a2908e18@dunslane.net> <200085.1741127335@sss.pgh.pa.us> <947e4acd-94b9-4990-83f5-874c71d69b17@dunslane.net>
Comments: In-reply-to Andrew Dunstan <andrew@dunslane.net>
	message dated "Tue, 04 Mar 2025 17:51:59 -0500"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <203684.1741129474.1@sss.pgh.pa.us>
Date: Tue, 04 Mar 2025 18:04:34 -0500
Message-ID: <203685.1741129474@sss.pgh.pa.us>
Archived-At: <https://www.postgresql.org/message-id/203685.1741129474%40sss.pgh.pa.us>
Precedence: bulk

Andrew Dunstan <andrew@dunslane.net> writes:
> Will check your patch out too.

Comparing previous run against current, I now see that my patch
caused it to skip these steps:

module-ldap_password_func-check 
module-pg_bsd_indent-check 
contrib-sepgsql-check 

Skipping the ldap and sepgsql tests is desirable, but it shouldn't
have skipped pg_bsd_indent.  I think the cause of that is that
src/tools/pg_bsd_indent isn't built in any of the previous build
steps.  Up to now it got built as a side-effect of invoking the
tests, which isn't great because any build errors/warnings disappear
into the install log which the script doesn't capture.  I agree
with not capturing the install log, because that's generally
uninteresting once we get past make-install; but we have to be sure
that everything gets built before that.

			regards, tom lane