We do a lot of our data viewing with browser-based programs and have excellent response times with almost everything... except looking up Work Order info from the main transaction table, INVTXN. Looking up the lines from a WO transaction can take a very long time (12 to 45 seconds, sometimes longer), when looking up serial number transactions takes a few tenths of a second.  
 
I have tried consolidating transactions, which dropped my number of records from ~400k down to ~290k, but there was no change in the time it takes to do WO look ups. Would I be right in assuming that, since WOPRE is not an indexed field and serial number is... that that has something to do with it? Which brings me to my real question: would a view that is indexed on WOPRE and WOSUF speed things up? I have a basic understanding of views and have requested them before, but I have not created one. Is it easy to do with PSQL?
 
But would that speed things up? Or would it be faster if I retrieved all of the rows into an array and then used PHP to select the rows I want? That seems like it should be slower. Maybe it would be faster if I suck the view into a MySQL table over night and then run the query from there instead? Sounds like a lot of experimenting. I thought I'd check with you folks and see if anyone knows offhand what would speed things up. Thanks.

Would it be possible to add wo_pre as an index in INVTXN and would that help query speed? Queries based on other indexed fields seem to be zippy, while looking for a WO # is terribly slow.