| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Alexander Law <exclusion(at)gmail(dot)com> |
| Cc: | "pgsql-docs(at)postgresql(dot)org" <pgsql-docs(at)postgresql(dot)org>, bruce(at)momjian(dot)us |
| Subject: | Re: Some minor error fixes |
| Date: | 2016-08-08 13:29:01 |
| Message-ID: | b09e00a5-1250-8cff-4370-ea67a4665cef@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2016-08-08 18:02:28 | Re: pg_trgm authors |
| Previous Message | tmaeke | 2016-08-08 12:37:02 | missing SQL BEGIN in example ECPG Program Accessing Large Objects |