From: | Erik Rijkers <er(at)xs4all(dot)nl> |
---|---|
To: | Teodor Sigaev <teodor(at)sigaev(dot)ru> |
Cc: | pgsql-committers(at)postgresql(dot)org, pgsql-committers-owner(at)postgresql(dot)org |
Subject: | Re: pgsql: Bloom index contrib module |
Date: | 2016-04-01 21:37:47 |
Message-ID: | bf87c5a78706f206392963be81231365@xs4all.nl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
On 2016-04-01 14:36, Erik Rijkers wrote:
> On 2016-04-01 15:49, Teodor Sigaev wrote:
>> Bloom index contrib module
>>
>> doc/src/sgml/bloom.sgml | 218 ++++++++++++++++++
>
The size of example table (in bloom.sgml):
CREATE TABLE tbloom AS
SELECT
random()::int as i1,
random()::int as i2,
[...]
random()::int as i12,
random()::int as i13
FROM
generate_series(1,1000);
seems too small to demonstrate the index-use.
For me, both on $BigServer at work as on $ModestDesktop at home the 1000
rows are not enough.
I suggest making the rowcount in that example a larger, for instance
10000, so: generate_series(1,10000).
Does that make sense? I realize the behavior is probably somewhat
dependent from hardware and settings...
thanks,
Erik Rijkers
From | Date | Subject | |
---|---|---|---|
Next Message | Noah Misch | 2016-04-02 01:56:12 | pgsql: Copyedit comments and documentation. |
Previous Message | Alvaro Herrera | 2016-04-01 21:36:35 | pgsql: test_slot_timelines: Fix alternate expected output |
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2016-04-01 21:39:01 | Re: pg_upgrade 9.6->9.6: column "amtype" does not exist |
Previous Message | Peter Geoghegan | 2016-04-01 21:37:19 | Re: pg_upgrade 9.6->9.6: column "amtype" does not exist |