Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bWkc8-0002YH-Br for pgsql-docs@arkaria.postgresql.org; Mon, 08 Aug 2016 13:29:08 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1bWkc7-00040m-VA for pgsql-docs@arkaria.postgresql.org; Mon, 08 Aug 2016 13:29:08 +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.84_2) (envelope-from ) id 1bWkc7-00040g-Id for pgsql-docs@postgresql.org; Mon, 08 Aug 2016 13:29:07 +0000 Received: from out2-smtp.messagingengine.com ([66.111.4.26]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1bWkc4-0001yQ-BW for pgsql-docs@postgresql.org; Mon, 08 Aug 2016 13:29:07 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 55651202F4; Mon, 8 Aug 2016 09:29:02 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute2.internal (MEProxy); Mon, 08 Aug 2016 09:29:02 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=IAxtpPIUMF9GxZ7 ZbByP1Ca/xto=; b=EhIi4vaRH2EzRiJ20icnlHX2OTCQdpG65Wa/7rW2HCBSgq4 +GYSATWMFkqyKRQ1UIkWQQlfigxeKxDvbZKwBS7UbmJbMQiS5nAcD3X4q7X0rfUy XnYTl3SvUZe7vLjpAudIURJk65ius2Hi/RufE32dphSBXaiBN3qsC7caRThw= X-Sasl-enc: rdyVXWouaFuWoPE8cpBn1BYaNXgfw6tPgRM3wIHhpwiM 1470662942 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 04127CCD84; Mon, 8 Aug 2016 09:29:01 -0400 (EDT) Subject: Re: Some minor error fixes To: Alexander Law References: <571470D8.50907@gmail.com> <88f42cdc-48fe-aeb9-60e7-e27587621a55@2ndquadrant.com> <572A09ED.8050204@gmail.com> <572A47DB.60304@gmail.com> <3b2f1642-7d31-f0e8-4ef1-9205d6fa5383@2ndquadrant.com> <5736C475.3030405@gmail.com> <5788613E.5020405@gmail.com> Cc: "pgsql-docs@postgresql.org" , bruce@momjian.us From: Peter Eisentraut Organization: 2ndQuadrant Message-ID: Date: Mon, 8 Aug 2016 09:29:01 -0400 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <5788613E.5020405@gmail.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-docs Precedence: bulk Sender: pgsql-docs-owner@postgresql.org On 7/15/16 12:06 AM, Alexander Law wrote: > Regarding 6, please look at the old documentation: > http://www.postgresql.org/docs/9.1/static/pgcrypto.html#PGCRYPTO-HASH-SPEED-TABLE > It contains "crypt-bf/5 | 211" in the table and "john -test shows 213 > loops/sec for crypt-bf/5" below the table. (The difference is 2 loops > per second). > > Current documentation: > https://www.postgresql.org/docs/current/static/pgcrypto.html#PGCRYPTO-HASH-SPEED-TABLE > contains: > "crypt-bf/5 13504" in the table (number is increased with the faster > CPU) and still "john -test shows 213 loops/sec for crypt-bf/5" below the > table. > So I propose to change 213 below the table to 13504 + 2 (previous > difference). makes sense, fixed -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs