This query from the console:
select * from stats order by start_time;
takes 8 seconds before starting its output. Am I wrong in assuming that
the index on start_time should make ORDER BY orders of magnitude
faster?
Or is this already fast enough? Or should I max up some memory (buffer)
Adam Rich wrote:
This query from the console:
select * from stats order by start_time;
takes 8 seconds before starting its output. Am I wrong in assuming that
the index on start_time should make ORDER BY orders of magnitude
faster?
Or is this already fast enough? Or should I max up some memory
Adam Rich [EMAIL PROTECTED] writes:
This query from the console:
select * from stats order by start_time;
takes 8 seconds before starting its output. Am I wrong in assuming that
the index on start_time should make ORDER BY orders of magnitude
faster?
Postgresql won't use the index for
However, if you limit the number of rows enough, you
might force it
to use an index:
select * from stats order by start_time limit 1000;
Thanks! Since LIMIT/OFFSET is the typical usage pattern for
a paginated
data set accessed from the Web (which is my case), it
immediately
On Mon, Aug 04, 2008 at 08:35:28AM -0500, Adam Rich wrote:
This query from the console:
select * from stats order by start_time;
takes 8 seconds before starting its output. Am I wrong in assuming that
the index on start_time should make ORDER BY orders of magnitude
faster?
