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 1g7Bju-0007AQ-CE for pgsql-hackers@arkaria.postgresql.org; Tue, 02 Oct 2018 03:52:50 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1g7Bjs-00058t-NX for pgsql-hackers@arkaria.postgresql.org; Tue, 02 Oct 2018 03:52:48 +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_SHA384:256) (Exim 4.89) (envelope-from ) id 1g7Bjs-00058m-GC for pgsql-hackers@lists.postgresql.org; Tue, 02 Oct 2018 03:52:48 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1g7Bjp-0001qg-QC for pgsql-hackers@lists.postgresql.org; Tue, 02 Oct 2018 03:52:48 +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 w923qUDn012778; Mon, 1 Oct 2018 23:52:30 -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> <8134.1538444333@sss.pgh.pa.us> Comments: In-reply-to Amit Kapila message dated "Tue, 02 Oct 2018 09:12:59 +0530" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <12776.1538452350.1@sss.pgh.pa.us> Date: Mon, 01 Oct 2018 23:52:30 -0400 Message-ID: <12777.1538452350@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Amit Kapila writes: > On Tue, Oct 2, 2018 at 7:08 AM Tom Lane wrote: >> 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 ... > Yeah, I was actually more worried about instability part, but now I > have tested it on both windows and centos machine and the test passes, > so I am okay with that. However, I feel if we want to go with that, > there is actually no need of statement "SET force_parallel_mode=1". OK, I hadn't tested to see if that could be dropped, but if it can, then we don't need it. The EXPLAIN is enough to ensure that the test is doing what we want. (I think we could drop the savepoint too, no?) regards, tom lane