Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bNuOZ-0000eA-Si for pgsql-docs@arkaria.postgresql.org; Fri, 15 Jul 2016 04:06:36 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1bNuOZ-00053z-G0 for pgsql-docs@arkaria.postgresql.org; Fri, 15 Jul 2016 04:06:35 +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 1bNuOZ-00053s-1K for pgsql-docs@postgresql.org; Fri, 15 Jul 2016 04:06:35 +0000 Received: from mail-lf0-x229.google.com ([2a00:1450:4010:c07::229]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1bNuOQ-0006wk-Lk for pgsql-docs@postgresql.org; Fri, 15 Jul 2016 04:06:34 +0000 Received: by mail-lf0-x229.google.com with SMTP id f93so78337683lfi.2 for ; Thu, 14 Jul 2016 21:06:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:from:cc:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=ceyWhusueB6cFiirH1e2vyKAub8sNC/HbjDHtiKCkuc=; b=QwKjhRKDGS/UaDd42VhLSARJCbrvgi2HuTUoqgmRmsL3en3sxT0twkbNQJk+3S2gGD iaNXNWiuCtgqmczUlyzf6R/1ym3OE+4GCGP8T4vzYo+xlA3XmSazqA+TiPs4noJ6VTZl 5sFZ56xVuFz/zDii34DF0m65R7eKUF9b7Q7iXB9FBQCJQIsRZfsX1fRwDABxm538IxGy 7j33hZ4UqQ69Cxbkwjpc2bndSFSPQ4jo4WWrGGikoCeTrleXqv05NVScNMFMROusNP9J AL7MeiPz0oxqs35R3Ry99rb9VaLawwzp7mGwSuTheHSOeeygnkjj+qputN1dnwT41XrB CVZw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:cc:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=ceyWhusueB6cFiirH1e2vyKAub8sNC/HbjDHtiKCkuc=; b=Bu7KE45GAGG4nkDWUOgqDsnWH625PSXQ2VTovpoRb2pHUqOrH5jXo959aC+w6I4jMK 16v0vIacoNRbdRWBk2/t8HgTPwi1wJmtOqMcmVUZCqeKrAbIHPNFXMedeVvIRUH4r4yh 8jgmIL2STknecrnjgtz6zwHy+xe0AiFeCxpSbVZP5W+PSQbfbjW53/EF2VTGCQsd2jV3 rjJdi1ah/AltFDYyRGW/P7j3mJqao/KRqoVxS/Vqt4ry0ZkLSxSSxzuJbfeivVyHksRB mRm3XQ4+Pkao0/lX4yGWD0yBJUMlkzHsyJgbRJT4dC6mrY6uAG76sJUST3VC/dHK5FBr 7B2A== X-Gm-Message-State: ALyK8tI4XXOmyGlh55p42VHQe8i+JOtEj42cNSuXOxdDCYboQHiWCnTwA0NHa0cNXoOPFw== X-Received: by 10.25.23.222 with SMTP id 91mr8401474lfx.38.1468555584870; Thu, 14 Jul 2016 21:06:24 -0700 (PDT) Received: from [1.0.0.7] ([109.196.196.155]) by smtp.gmail.com with ESMTPSA id q195sm1433388lfe.33.2016.07.14.21.06.23 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 14 Jul 2016 21:06:24 -0700 (PDT) Subject: Re: Some minor error fixes To: Peter Eisentraut 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> From: Alexander Law Cc: "pgsql-docs@postgresql.org" , bruce@momjian.us Message-ID: <5788613E.5020405@gmail.com> Date: Fri, 15 Jul 2016 07:06:22 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Pg-Spam-Score: -2.7 (--) 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 Thank you, Peter. Regarding 1, you're right, I didn't see "per row" in that sentence and decided that it was total overhead (and then again I should change nsec to msec). 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). Or maybe we should rerun all the benchmarks and update all the numbers (see commit d6464fdc). Best wishes, Alexander 15.07.2016 05:36, Peter Eisentraut пишет: > On 5/14/16 2:23 AM, Alexander Law wrote: >> Please look at the following errors/fixes. > I've applied 2, 3, 4, 5. > > 1 was correct according to my math. (115.9-9.8)/100000*1000*1000 = 1061 > > 6 looked too complicated to me. ;-) Can you explain where you got your > number from? > -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs