From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
---|---|
To: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru> |
Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [HACKERS] A design for amcheck heapam verification |
Date: | 2018-02-08 17:45:13 |
Message-ID: | CAH2-WzmuFy88vjntz1+_AmMfLVcvzaVsn8NBucv1+CTeU1dDEQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Feb 8, 2018 at 6:05 AM, Andrey Borodin <x4mmm(at)yandex-team(dot)ru> wrote:
> I do not see a reason behind hashing the seed.
It made some sense when I was XOR'ing it to mix. A uniform
distribution of bits seemed desirable then, since random() won't use
the most significant bit -- it generates random numbers in the range
of 0 to 2^31-1. It does seem unnecessary now.
> Also, I'd like to reformulate this paragraph. I understand what you want to say, but the sentence is incorrect.
> + * The Bloom filter behaves non-deterministically when caller passes a random
> + * seed value. This ensures that the same false positives will not occur from
> + * one run to the next, which is useful to some callers.
> Bloom filter behaves deterministically, but differently. This does not ensures any thing, but probably will give something with hight probability.
I agree that that's unclear. I should probably cut it down, and say
something like "caller can pass a random seed to make it unlikely that
the same false positives will occur from one run to the next".
--
Peter Geoghegan
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2018-02-08 17:48:34 | Re: Proposal: partition pruning by secondary attributes |
Previous Message | David Steele | 2018-02-08 17:04:44 | Re: New gist vacuum. |