suhas.basavaraj12 <suha...@verse.in> wrote: > This was observed in postgres 9.0.1.
You might want to review the bug fixes in 9.0 maintenance releases and see if any of them could be responsible for what you saw: http://www.postgresql.org/docs/9.0/static/release-9-0-2.html http://www.postgresql.org/docs/9.0/static/release-9-0-3.html http://www.postgresql.org/docs/9.0/static/release-9-0-4.html http://www.postgresql.org/docs/9.0/static/release-9-0-5.html http://www.postgresql.org/docs/9.0/static/release-9-0-6.html http://www.postgresql.org/docs/9.0/static/release-9-0-7.html http://www.postgresql.org/docs/9.0/static/release-9-0-8.html http://www.postgresql.org/docs/9.0/static/release-9-0-9.html http://www.postgresql.org/docs/9.0/static/release-9-0-10.html http://www.postgresql.org/docs/9.0/static/release-9-0-11.html http://www.postgresql.org/docs/9.0/static/release-9-0-12.html ... or just apply all of those bug fixes and see if you can make it happen again. In general, it pays to apply fixes as they become available. http://www.postgresql.org/support/versioning/ -- Kevin Grittner EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
