something like this with (nolock)
i.e. select count(*) from customers (nolock) where
name like 'Mark%'
Regardless, I'm very impressed with PostgreSQL and I
think we're moving ahead with it.
Mark
--- Bruno Wolff III <[EMAIL PROTECTED]> wrote:
> On Tue, May 24, 2005
First, thanks for all the helpful replies. I've
listened to the suggestions and done some more digging
and have results:
I did show_plan_all in MSSQL and found that it was
doing an Index Scan. I've read someplace that if the
data you need is all in the index, then MSSQL has a
feature/hack where it
> Post the result of this for us:
>
> explain analyze select count(*) from mtable where
> day='Mon';
>
> On both machines.
Hi Chris --
PostgreSQL Machine:
"Aggregate (cost=140122.56..140122.56 rows=1 width=0)
(actual time=24516.000..24516.000 rows=1 loops=1)"
" -> Index Scan using "day" on m
Hi,
I have some experience with MSSQL and am examining
PostgreSQL. I'm running under Windows. I like what I
see so far, but I'm hoping for some performance
advice:
1. My test database has 7 million records.
2. There are two columns - an integer and a char
column called Day which has a random val
