Hi - I'm not a particularly experienced dba, so I'm hoping this isn't a ridiculous question. I have a 5 GB table with lots of churn in a 14 GB database. Querying this one table without limits has just started throwing "out of memory for query" from multiple clients (psql, java). I'm working with the developers to look at it from the client side, but I'm wondering if either partitioning the table or more aggressive vacuuming of this table would have an effect on the out of memory problem. I'm running 8.3.5 on solaris 10. Thanks! Mija CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential, proprietary, and/or privileged information protected by law. If you are not the intended recipient, you may not use, copy, or distribute this e-mail message or its attachments. If you believe you have received this e-mail message in error, please contact the sender by reply e-mail and destroy all copies of the original message. -- Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
