Tom --
<...> >> A cron job dropdb one of the databases and createdb it and then pg_restore. > Roughly 80GB dump. > > So far, my guess is that this is fixed by commits a1f064fc2 + d7598aeea. > >> Out production PostgreSQL running a 9.1 variant does not have this problem. > It does not have the nightly dropdb/createdb/pg_restore, but otherwise > similar > usage patterins. It is also configured to use more memory. > > 9.1 has the same bug (and the same patches), but I think that the aspect > you're running into is specific to DROP DATABASE scenarios. > Is there any idea of when this will be released ? Thanks, Greg W. -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
