Re: [PERFORM] Postgres server getting slow!!

2005-01-30 Thread Joshua D. Drake
N S wrote: I checked to find out the cause of the problem, ppp is disconnecting properly and the user session is also closed smoothely. But when a report query is run on the table containing 32500 records, the memory shoots up from 50 MB to 500 MB(Total memory is 512 MB RAM). After that the memory

Re: [PERFORM] Postgres server getting slow!!

2005-01-30 Thread N S
I checked to find out the cause of the problem, ppp is disconnecting properly and the user session is also closed smoothely. But when a report query is run on the table containing 32500 records, the memory shoots up from 50 MB to 500 MB(Total memory is 512 MB RAM). After that the memory usage neve

Re: [PERFORM] Performance problem with semi-large tables

2005-01-30 Thread Tom Lane
PFC <[EMAIL PROTECTED]> writes: >> For example, let's add another filter to get all the shipments with >> release code '5' that are 7 days old or newer. >> >> ss.date >= current_date - 7 > It's the order by + limit which makes the query behaves badly, and > which > forces use of kludge

Re: [PERFORM] Performance problem with semi-large tables

2005-01-30 Thread PFC
SELECT * FROM shipment_status WHERE release_code_id = constant ORDER BY release_code_id DESC, date DESC LIMIT 100; I have done this in other queries where sorting by both release code and date were important. You are right, it is very fast and I do have this index in play. However, most of t