Received: from malur.postgresql.org ([2a02:16a8:dc51::56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1g79f1-0001L1-Sw for pgsql-hackers@arkaria.postgresql.org; Tue, 02 Oct 2018 01:39:40 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1g79f0-0007KK-4N for pgsql-hackers@arkaria.postgresql.org; Tue, 02 Oct 2018 01:39:38 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1g79ez-0007KC-LI for pgsql-hackers@lists.postgresql.org; Tue, 02 Oct 2018 01:39:37 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1g79ex-0003T7-4y for pgsql-hackers@lists.postgresql.org; Tue, 02 Oct 2018 01:39:36 +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 w921crYP008135; Mon, 1 Oct 2018 21:38:53 -0400 From: Tom Lane To: Amit Kapila cc: Thomas Munro , PostgreSQL Hackers , hlinnaka Subject: Re: SerializeParamList vs machines with strict alignment In-reply-to: References: <11629.1536550032@sss.pgh.pa.us> <8352.1536586500@sss.pgh.pa.us> <27748.1538425312@sss.pgh.pa.us> <28627.1538426947@sss.pgh.pa.us> <4694.1538438514@sss.pgh.pa.us> Comments: In-reply-to Amit Kapila message dated "Tue, 02 Oct 2018 06:56:45 +0530" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <8133.1538444333.1@sss.pgh.pa.us> Date: Mon, 01 Oct 2018 21:38:53 -0400 Message-ID: <8134.1538444333@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Amit Kapila writes: > I think if we do Analyze on the table after populating rows, it should > use just one worker and that should be sufficient to hit the case > being discussed. I would like to change the test so that it uses just > one worker. I thought that adding an ANALYZE would make the test be net slower, not faster; ANALYZE isn't free, even on just a row or so. Also, I believe that coding the test this way makes the leader send the param values to multiple workers, which would flush out any problems with serializing a value multiple times. As against that, there's a hazard that the number of workers might not be stable ... but it seems like we have lots of other occurrences of that same hazard elsewhere in this test script. regards, tom lane