DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type:Message-ID;
	b=nTJl9+JaXfps8S6zNE0ZWNmztM0JyC831WDCqy+fAZBYi03HNJ9BvTLAggwEu9Yzp6KSkqire8CHFLcFsaX1dCJzldJEiDFrbKFFs/S9gskCRoowcQmjB9yeEuHCMUnfMmYLLLFTd6ZDUz6qOyyKX07CKhfJo0dM2w10/rgCizY=;
Date: Wed, 30 May 2007 11:55:05 -0700 (PDT)
From: Trigve Siver <trigves@yahoo.com>
Subject: Re: slow query execution
To: pgsql-sql@postgresql.org
MIME-Version: 1.0
Content-Type: text/plain; charset=ascii
Message-ID: <979338.47402.qm@web52707.mail.re2.yahoo.com>

>----- Original Message ----
>From: Andrew Sullivan <ajs@crankycanuck.ca>
>To: pgsql-sql@postgresql.org
>Sent: Wednesday, May 30, 2007 8:30:32 PM
>Subject: Re: [SQL] slow query execution
>
>On Wed, May 30, 2007 at 11:08:02AM -0700, Trigve Siver wrote:
>
>> I want to do it only for some queries. So when I need query like
>> that "SELECT * from t1" I need to add row_numbers there. So I will
>> have "query with row_numbers" (where row_numbers are row numbers of
>> my virtual list view). Then when I perform search I also get
>> row_numbers for IDs of search result and I can highlight items in
>> my list view. I haven't found other solution that met my
>> requirements.
>
>You really need to ensure you keep that ORDER BY in there, then.  The
>order that SQL returns in is not determined until the data has come
>back.  Are you doing this all in one serialisable transaction,
>though?  If not, what guarantee will you have that new data won't
>mess up your row numbering from query to query?

I seee...when new data will be added to table, then row numbers wouldn''t be valid anymore.

Hmmm...looked like I need to find other solution.

thanks

Trigve


____________________________________________________________________________________Get the free Yahoo! toolbar and rest assured with the added security of spyware protection.
http://new.toolbar.yahoo.com/toolbar/features/norton/index.php