Re: Extending the volume size of the data directory volume

From: Scott Mead <scottm(at)openscg(dot)com>
To: panam <panam(at)gmx(dot)net>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Extending the volume size of the data directory volume
Date: 2011-11-30 23:04:29
Message-ID: CAKq0gv+jWq_6-Nsebw7kJKMKPEtyhUaivPWOYBQGtBhanNVK0w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Nov 30, 2011 at 4:19 PM, panam <panam(at)gmx(dot)net> wrote:

> Had to restart the import. This time, I tried with a smaller initial disk
> size (1GB) and extended it dynamically. It did not cause any problems.
> A different reason might be, that I remounted the volume in between during
> the last update to deactivate buffer flushing. Maybe a bad combination.
> Let's see how far it gets this time...
>
>
If you remounted without restarting postgres, I would say "that's your
problem"

--JT

>
> --
> View this message in context:
> http://postgresql.1045698.n5.nabble.com/Extending-the-volume-size-of-the-data-directory-volume-tp5030663p5036767.html
> Sent from the PostgreSQL - general mailing list archive at Nabble.com.
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tomas Vondra 2011-11-30 23:41:15 Re: Query Optimizer makes a poor choice
Previous Message Tyler Hains 2011-11-30 22:22:03 Re: Query Optimizer makes a poor choice