Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rfI45-00GiPQ-Ar for pgsql-hackers@arkaria.postgresql.org; Wed, 28 Feb 2024 11:25:34 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1rfI43-009YOA-UR for pgsql-hackers@arkaria.postgresql.org; Wed, 28 Feb 2024 11:25:32 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rfI43-009YO1-Gu for pgsql-hackers@lists.postgresql.org; Wed, 28 Feb 2024 11:25:32 +0000 Received: from meesny.iki.fi ([195.140.195.201]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rfI41-001kSX-26 for pgsql-hackers@postgresql.org; Wed, 28 Feb 2024 11:25:31 +0000 Received: from [172.20.6.221] (unknown [178.134.136.147]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: hlinnaka) by meesny.iki.fi (Postfix) with ESMTPSA id 4TlBq5358GzyTh; Wed, 28 Feb 2024 13:25:21 +0200 (EET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iki.fi; s=meesny; t=1709119525; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=c+f0j2kYBSWHyjAwDSibWET1f1XztDbp1Xaeey4W3RE=; b=KQ+zyCPnXrh9cvGsEtc3TUbHmhIy/rJRltGwILjFRqv3DFGZnknGjSv/ASpA7BWmStZ1PT Z64ejj96kMYmsdvN9NSmiLSD8o0y/EVfCN/6MVc1LBpQ+YVK0PqgnqpNKTVn5a7gsGiPs9 ytxEcrf+3+JIEepcVC9lbb7Ls3lJvHg= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=iki.fi; s=meesny; t=1709119525; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=c+f0j2kYBSWHyjAwDSibWET1f1XztDbp1Xaeey4W3RE=; b=KXPvdcYjhqWV8xosYsdEZu/L4s6NWaaDn/KaH1ey1Q9h6Zry9XWDbiSwUwwLUgUeye2wJJ p2zN3SyQWNTsEVBU50ZaMngoqCgV0n931o3fXLXWKR0EmhfzbpD8opb7mE3ICChcFOSoZ4 MWaO4MjhxnkffiS1NzJqR+Zp9xQORqM= ARC-Authentication-Results: i=1; ORIGINATING; auth=pass smtp.auth=hlinnaka smtp.mailfrom=hlinnaka@iki.fi ARC-Seal: i=1; s=meesny; d=iki.fi; t=1709119525; a=rsa-sha256; cv=none; b=WvZPdP4rPrWHtNWwle7gn15m4UEoI1GSMI0ReSatW9OWtdqtQrSMD/VDQ8d8Rrnn25A6xs r6MmLIdlY7aEuRI8QxG2BO+RxaZTeGWb4HSMli4hpd32SHIh4co8BW0fv5Js7StC6Q8EhU YXCeHU3SW/bnSP8ed5blKeozwJYFWgw= Message-ID: Date: Wed, 28 Feb 2024 15:25:19 +0400 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Relation bulk write facility Content-Language: en-US To: Andres Freund , Thomas Munro , Noah Misch Cc: Michael Paquier , Robert Haas , Tom Lane , Peter Smith , vignesh C , pgsql-hackers , Melanie Plageman References: <20240224212936.f3zcbs24f7oaapm4@alap3.anarazel.de> <0C469A7A-548C-4B0C-9495-730FE80046E1@iki.fi> <31db8d41-2ac9-4b5e-b7a8-712d6d7d7aa2@iki.fi> <20240225194322.a5@rfd.leadboat.com> <1535845.1708890691@sss.pgh.pa.us> <3a0d22fa-7613-4881-aa19-ddd31fb92cc0@iki.fi> <20240228092642.i23w4qzdsuy6da6y@alap3.anarazel.de> From: Heikki Linnakangas In-Reply-To: <20240228092642.i23w4qzdsuy6da6y@alap3.anarazel.de> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Committed, after fixing the various little things you pointed out: On 28/02/2024 00:30, Thomas Munro wrote: > --- a/doc/src/sgml/installation.sgml > +++ b/doc/src/sgml/installation.sgml > @@ -3401,7 +3401,7 @@ export MANPATH > > PostgreSQL can be expected to work on current > versions of these operating systems: Linux, Windows, > - FreeBSD, OpenBSD, NetBSD, DragonFlyBSD, macOS, AIX, Solaris, and illumos. > + FreeBSD, OpenBSD, NetBSD, DragonFlyBSD, macOS, Solaris, and illumos. > > There is also a little roll-of-honour of operating systems we used to > support, just a couple of paragraphs down, where AIX should appear. Added. On 28/02/2024 05:52, Noah Misch wrote: > Regardless of how someone were to step up to maintain it, we'd be telling them > such contributions have negative value and must stop. We're expelling AIX due > to low demand, compiler bugs, its ABI, and its shlib symbol export needs. Reworded. >> Apperently the "pg_attribute_aligned(a)" attribute doesn't work on AIX >> (linker?) for values larger than PG_IO_ALIGN_SIZE. > > No; see https://postgr.es/m/20240225194322.a5%40rfd.leadboat.com Ok, reworded. On 28/02/2024 11:26, Andres Freund wrote: > On 2024-02-28 00:24:01 +0400, Heikki Linnakangas wrote: > The problem is due to this hunk: >> @@ -401,10 +376,6 @@ install-lib-static: $(stlib) installdirs-lib >> >> install-lib-shared: $(shlib) installdirs-lib >> ifdef soname >> -# we don't install $(shlib) on AIX >> -# (see http://archives.postgresql.org/message-id/52EF20B2E3209443BC37736D00C3C1380A6E79FE@EXADV1.host.magwien.gv.at) >> -ifneq ($(PORTNAME), aix) >> - $(INSTALL_SHLIB) $< '$(DESTDIR)$(libdir)/$(shlib)' >> ifneq ($(PORTNAME), cygwin) >> ifneq ($(PORTNAME), win32) >> ifneq ($(shlib), $(shlib_major)) > > So the versioned name didn't end up getting installed anymore, leading to > broken symlinks in the install directory. Fixed, thanks! >> diff --git a/src/bin/pg_basebackup/t/010_pg_basebackup.pl b/src/bin/pg_basebackup/t/010_pg_basebackup.pl >> index 86cc01a640b..fc6b00224f6 100644 >> --- a/src/bin/pg_basebackup/t/010_pg_basebackup.pl >> +++ b/src/bin/pg_basebackup/t/010_pg_basebackup.pl >> @@ -400,9 +400,6 @@ is(scalar(@tblspc_tars), 1, 'one tablespace tar was created'); >> SKIP: >> { >> my $tar = $ENV{TAR}; >> - # don't check for a working tar here, to accommodate various odd >> - # cases such as AIX. If tar doesn't work the init_from_backup below >> - # will fail. >> skip "no tar program available", 1 >> if (!defined $tar || $tar eq ''); > > Maybe better to not remove the whole comment, just the reference to AIX? Ok, done >> diff --git a/src/test/regress/sql/sanity_check.sql b/src/test/regress/sql/sanity_check.sql >> index 7f338d191c6..2e9d5ebef3f 100644 >> --- a/src/test/regress/sql/sanity_check.sql >> +++ b/src/test/regress/sql/sanity_check.sql >> @@ -21,12 +21,15 @@ SELECT relname, relkind >> AND relfilenode <> 0; >> >> -- >> --- When ALIGNOF_DOUBLE==4 (e.g. AIX), the C ABI may impose 8-byte alignment on >> +-- When MAXIMUM_ALIGNOF==8 but ALIGNOF_DOUBLE==4, the C ABI may impose 8-byte alignment >> -- some of the C types that correspond to TYPALIGN_DOUBLE SQL types. To ensure >> -- catalog C struct layout matches catalog tuple layout, arrange for the tuple >> -- offset of each fixed-width, attalign='d' catalog column to be divisible by 8 >> -- unconditionally. Keep such columns before the first NameData column of the >> -- catalog, since packagers can override NAMEDATALEN to an odd number. >> +-- (XXX: I'm not sure if any of the supported platforms have MAXIMUM_ALIGNOF==8 and >> +-- ALIGNOF_DOUBLE==4. Perhaps we should just require that >> +-- ALIGNOF_DOUBLE==MAXIMUM_ALIGNOF) >> -- >> WITH check_columns AS ( >> SELECT relname, attname, > > I agree, this should be an error, and we should then remove the test. Done. -- Heikki Linnakangas Neon (https://neon.tech)