From: mark@mark.mielke.cc
To: Harry Jackson <harryjackson@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Suspending SELECTs
Date: Wed, 18 Jan 2006 11:50:17 -0500
Message-ID: <20060118165017.GA10026@mark.mielke.cc> (raw)
In-Reply-To: <45b42ce40601180741q34553beeu134da075987e8232@mail.gmail.com>
References: <43CB71AC.20203@barettadeit.com>
<9766.1137433907@sss.pgh.pa.us>
<43CD4BD0.9090807@barettadeit.com>
<20060117211259.GA13926@mark.mielke.cc>
<43CE030E.1070707@barettadeit.com>
<20060118143024.GA8402@mark.mielke.cc>
<43CE5AC7.50407@barettadeit.com>
<45b42ce40601180741q34553beeu134da075987e8232@mail.gmail.com>
On Wed, Jan 18, 2006 at 03:41:57PM +0000, Harry Jackson wrote:
> There are various reason why google might want to limit the search
> result returned ie to encourage people to narrow their search. Prevent
> screen scrapers from hitting them really hard blah blah. Perhaps less
> than 0.00000001% of real users (not scrapers) actually dig down to the
> 10th page so whats the point.
I recall a day when google crashed, apparently due to a Windows virus
that would use google to obtain email addresses.
As an unsubstantiated theory - this may have involved many, many clients,
all accessing search page results beyond the first page.
I don't see google optimizing for the multiple page scenario. Most
people (as I think you agree above), are happy with the first or
second page, and they are gone. Keeping a cursor for these people as
anything more than an offset into search criteria, would not be
useful.
Cheers,
--
mark@mielke.cc / markm@ncf.ca / markm@nortel.com __________________________
. . _ ._ . . .__ . . ._. .__ . . . .__ | Neighbourhood Coder
|\/| |_| |_| |/ |_ |\/| | |_ | |/ |_ |
| | | | | \ | \ |__ . | | .|. |__ |__ | \ |__ | Ottawa, Ontario, Canada
One ring to rule them all, one ring to find them, one ring to bring them all
and in the darkness bind them...
http://mark.mielke.cc/
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: mark@mark.mielke.cc, harryjackson@gmail.com
Subject: Re: Suspending SELECTs
In-Reply-To: <20060118165017.GA10026@mark.mielke.cc>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox