Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1gHCSv-000164-5n for pgsql-bugs@arkaria.postgresql.org; Mon, 29 Oct 2018 18:40:41 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gHCSt-0007Ew-Ln for pgsql-bugs@arkaria.postgresql.org; Mon, 29 Oct 2018 18:40:39 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1gHCSt-0007Em-CQ for pgsql-bugs@lists.postgresql.org; Mon, 29 Oct 2018 18:40:39 +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 1gHCSq-0000Tk-SG for pgsql-bugs@lists.postgresql.org; Mon, 29 Oct 2018 18:40:38 +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 w9TIdpsS017827; Mon, 29 Oct 2018 14:39:52 -0400 From: Tom Lane To: Peter Geoghegan cc: paul.vanderlinden@mapcreator.eu, PostgreSQL mailing lists , Heikki Linnakangas Subject: Re: BUG #15460: Error while creating index or constraint In-reply-to: References: <15460-b6db80de822fa0ad@postgresql.org> <27191.1540827070@sss.pgh.pa.us> <8330.1540831863@sss.pgh.pa.us> Comments: In-reply-to Peter Geoghegan message dated "Mon, 29 Oct 2018 17:11:57 -0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <17825.1540838391.1@sss.pgh.pa.us> Date: Mon, 29 Oct 2018 14:39:51 -0400 Message-ID: <17826.1540838391@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Peter Geoghegan writes: > On Mon, Oct 29, 2018 at 4:51 PM Tom Lane wrote: >> That's a poor excuse for ignoring the message style guidelines. >> There are many reasons why even experts could get confused trying >> to follow badly-written messages. > I'll change the trace_sort messages to refer to "worker n" -- that > should bring the trace_sort output in line with our style guidelines. WFM. regards, tom lane