Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gyJdr-0004EH-OB for pgsql-hackers@arkaria.postgresql.org; Mon, 25 Feb 2019 17:02:11 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gyJdp-0002YD-Hg for pgsql-hackers@arkaria.postgresql.org; Mon, 25 Feb 2019 17:02:09 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gyJdp-0002Y6-AV for pgsql-hackers@lists.postgresql.org; Mon, 25 Feb 2019 17:02:09 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gyJdi-0001nF-Ts; Mon, 25 Feb 2019 17:02:08 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id x1PH20FZ032369; Mon, 25 Feb 2019 12:02:00 -0500 From: Tom Lane To: Amit Kapila cc: pgsql-hackers@lists.postgresql.org Subject: Re: pgsql: Avoid creation of the free space map for small heap relations, t In-reply-to: References: Comments: In-reply-to Amit Kapila message dated "Mon, 04 Feb 2019 02:22:49 +0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <32367.1551114120.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Mon, 25 Feb 2019 12:02:00 -0500 Message-ID: <32368.1551114120@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Amit Kapila writes: > Avoid creation of the free space map for small heap relations, take 2. I think this patch still has some issues. Note the following two recent buildfarm failures: https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=3Dpetalura&dt=3D20= 19-02-20%2004%3A20%3A01 https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=3Ddragonet&dt=3D20= 19-02-24%2022%3A48%3A02 Both of them failed in an assertion added by this patch: TRAP: FailedAssertion("!((rel->rd_rel->relkind =3D=3D 'r' || rel->rd_rel->= relkind =3D=3D 't') && fsm_local_map.map[oldPage] =3D=3D 0x01)", File: "/h= ome/bf/build/buildfarm-petalura/HEAD/pgsql.build/../pgsql/src/backend/stor= age/freespace/freespace.c", Line: 229) ... 2019-02-20 06:23:26.660 CET [5c6ce440.3bd2:4] LOG: server process (PID 17= 981) was terminated by signal 6: Aborted 2019-02-20 06:23:26.660 CET [5c6ce440.3bd2:5] DETAIL: Failed process was = running: INSERT INTO T VALUES ( $1 ) I can even offer you a theory as to why we're managing to get through all the core regression tests and then failing in ecpg: the failing test is ecpg/test/thread/prep.pgc, and I think that may be the only place in our tests where we stress concurrent insertions into a single small table. So I think you've got race-condition issues here. It might or might not be significant that these two animals are part of Andres' JIT-enabled menagerie. I could see that affecting test timing to the point of showing a symptom that's otherwise hard to hit. regards, tom lane