We have a Java client that is using JDBC to communicate with the Postgres database. We have a stored procedure, foo, that is written in C which returns a byte array (bytea) to the Java client. This function takes in a couple of integers and based upon their values can return a byte array or no da
We are suffering from the same issue that is described in this email thread http://archives.postgresql.org/pgsql-general/2005-07/msg00486.php.
I don't know if this is the appropriate place to make this request, so if not, please forgive me. However, in our particular case, we don't have enou
> This isn't what you asked for, but if you can afford a modest amount of downtime you could always drop/recreate the indexes.
Unfortunately, we cannot afford any down time. That is why we are looking to pay someone to help us implement Tom Lane's suggested solution.
Brent
>Have you tried vacuuming more frequently?
Yes, we vacuum every 45-60 minutes. We boarder on having a vacuum running continuously vacuuming some table in the database.
Brent
