The larger the table, the more you as the developer have to think about how to construct better sql statments.

I use a table with over 250,000 records, and take back only say 40-60 records. and its blazing..

The key is that you construct your querry, you try to get as few records, as possible back... letting the server 'filter' out as much non needed data, and just use your client app to display the results that you actually need.

Bob

>Hi Bob Lee
>
>I think the next thing is to use it a little and see if everythings working alright. I wonder how it would performs over a slow modem connection? I wonder if their would be any noticeable degradation if there were 50,000 records, or 250,000, etc. As soon as I have a little more time, I will import some records from my Software - Master Application via comma delimited text file for some test. Please feel free to experiment with the testorders table all you want. You can add, delete, update, etc.
>
>I spent some time with the pg_hba.conf file and made all my other tables so a password is needed to access them. Hopefully this will prevent any accidents to my other tables; although, I don't really have anything of value in the postgres area right now, other than what I have built up as learning tools. Thanks for your help and I'll check back tomarrow.