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 1ghcjP-0000wf-OV for pgsql-hackers@arkaria.postgresql.org; Thu, 10 Jan 2019 15:58:55 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1ghcjM-0008LL-PK for pgsql-hackers@arkaria.postgresql.org; Thu, 10 Jan 2019 15:58:52 +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 1ghcjM-0008LB-Hs for pgsql-hackers@lists.postgresql.org; Thu, 10 Jan 2019 15:58:52 +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 1ghcjI-0004pB-TF for pgsql-hackers@postgresql.org; Thu, 10 Jan 2019 15:58:51 +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 x0AFwVq2006341; Thu, 10 Jan 2019 10:58:31 -0500 From: Tom Lane To: Dean Rasheed cc: PostgreSQL Hackers Subject: Re: Policy on cross-posting to multiple lists In-reply-to: References: Comments: In-reply-to Dean Rasheed message dated "Thu, 10 Jan 2019 09:56:30 +0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <6339.1547135911.1@sss.pgh.pa.us> Date: Thu, 10 Jan 2019 10:58:31 -0500 Message-ID: <6340.1547135911@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Dean Rasheed writes: > Has the policy on cross-posting to multiple lists been hardened recently? Not that I've heard of. > The "Crash on ALTER TABLE" thread [1] started on -bugs, but Andrew's > message on 8 Jan with an initial proposed patch and my response later > that day both CC'ed -hackers and seem to have been rejected, and so > are missing from the archives. I've done the same recently, without problems. I'd suggest inquiring on the pgsql-www list; project infrastructure issues are not really on-topic here. regards, tom lane