Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Query only slow on first run
- From: cluster <skrald(at)amossen(dot)dk>
- To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: pgsql-performance(at)postgresql(dot)org
- Subject: Re: Query only slow on first run
- Date: Thu, 29 Nov 2007 12:07:37 +0100
You're essentially asking for a random sample of data that is not currently in memory. You're not going to get that without some I/O.
No, that sounds reasonable enough. But do you agree with the statement that my query will just get slower and slower over time as the number of posts increases while the part having status = 1 is constant? (Therefore, as the relevant fraction becomes smaller over time, the "Filter: status = 1" operation becomes slower.)
- Follow-Ups:
- Re: Query only slow on first run
- From: Tom Lane
- Re: Query only slow on first run
- References:
- Query only slow on first run
- From: cluster
- Re: Query only slow on first run
- From: Andrew Sullivan
- Re: Query only slow on first run
- From: Tom Lane
- Re: Query only slow on first run
- From: cluster
- Re: Query only slow on first run
- From: Dave Dutcher
- Re: Query only slow on first run
- From: cluster
- Re: Query only slow on first run
- From: Steinar H. Gunderson
- Re: Query only slow on first run
- From: Tom Lane
- Re: Query only slow on first run
- From: tmp
- Re: Query only slow on first run
- From: cluster
- Re: Query only slow on first run
- From: Steinar H. Gunderson
- Re: Query only slow on first run
- From: cluster
- Re: Query only slow on first run
- From: Tom Lane
- Query only slow on first run
- Prev by Date: Re: Query only slow on first run
- Next by Date: Re: TB-sized databases
- Previous by thread: Re: Query only slow on first run
- Next by thread: Re: Query only slow on first run
- Indexes: