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 1f1MRo-0005zc-8g for pgsql-docs@arkaria.postgresql.org; Thu, 29 Mar 2018 01:33:48 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1f1MRm-0007cw-Oz for pgsql-docs@arkaria.postgresql.org; Thu, 29 Mar 2018 01:33:46 +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 1f1MRm-0007cn-G7 for pgsql-docs@lists.postgresql.org; Thu, 29 Mar 2018 01:33:46 +0000 Received: from out5-smtp.messagingengine.com ([66.111.4.29]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1f1MRj-00060F-0a for pgsql-docs@lists.postgresql.org; Thu, 29 Mar 2018 01:33:44 +0000 Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id CFD7620FF9; Wed, 28 Mar 2018 21:33:41 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute7.internal (MEProxy); Wed, 28 Mar 2018 21:33:41 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=f3loVO wMA0jycYGzWjYqRmjKDdWfvX8GuChBockHXjs=; b=At+O6TxRBcs/s70FtqI8Sq 8Lc2WW4nSGr60OkqC1lSIkMMZk3Q55xcBKOyA6qqP/GlljjBTwmw9zzDTi8Nd9zZ cmGsoQ4oNhRIqv1KwbgdOzfh/3+uRr1ChdMO4vmmVQN4GZ+HEEpY8X1KsCxlUx/U NZmAfTjlEg7uTuB+OYnEEmVI1o0wTc0D0ZKjCcewcqh/2LKBhlbYETzl9Pv0cqq+ cwaZBLMQJlRHOHQT2r/gmVm5Z4tjTUtozVCFErjJWlqwEt5IkbzSEu/r2X+Z3z47 2UninUS4Ipj9ugYAj6tDyxfpJ9/Amx9nVETNsKZbU7zjK3l5a+sP1KFjUHu7EmjQ == X-ME-Sender: Received: from april.local (c-73-13-66-39.hsd1.pa.comcast.net [73.13.66.39]) by mail.messagingengine.com (Postfix) with ESMTPA id 9044C10251; Wed, 28 Mar 2018 21:33:41 -0400 (EDT) Subject: Re: need for SHA3 To: ppkrauss@gmail.com, pgsql-docs@lists.postgresql.org References: <152198134663.32649.5037088128115567926@wrigleys.postgresql.org> From: Peter Eisentraut Organization: 2ndQuadrant Message-ID: <03ae36da-9f74-d7c5-8551-b5fbc4190836@2ndquadrant.com> Date: Wed, 28 Mar 2018 21:33:41 -0400 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <152198134663.32649.5037088128115567926@wrigleys.postgresql.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 3/25/18 08:35, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/10/static/pgcrypto.html > Description: > > In nowadays SHA3 is so important tham SHA2 family... Whow to vote +1 or > request it? This form is for reporting issues with the documentation. We don't really have a feature request system. If you want it, you need to implement it or find someone to do it. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services