On Oct 15, 2012, at 2:27 AM, Tom Lane wrote:
> Tore Halset writes:
>> On this box I drop a 80GB database each night followed by a restore of a
>> similar sized database. It is a restore of our production database to a
>> development server. This box is running 9.2rc1 (sorry).
>
>> du and df r
Tore Halset writes:
> On Oct 15, 2012, at 2:27 AM, Tom Lane wrote:
>> Tore Halset writes:
>>> On this box I drop a 80GB database each night followed by a restore of a
>>> similar sized database. It is a restore of our production database to a
>>> development server. This box is running 9.2rc1
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
Greg Williamson writes:
>> So far, my guess is that this is fixed by commits a1f064fc2 + d7598aeea.
> Is there any idea of when this will be released ?
No. I'd guess that there will be update releases before the end of the
year, but they are not imminent. We have some open issues that have to
