On Wed, June 1, 2016 3:45 am, Markus Rosjat wrote: > Hi there, > > just need some kind of acknowledgement for my workflow :) > > a naive approach would be: > > - extend the virtual disk > - create a partition /var/postgresql (thats the folder under var right > now) > - move the files to the new partition > - hope it works :-P > > So hope someone with experience in such scenario can give me a hint or too > >
You're working with virtual machines? What I do is put /var/postgresql on it's own virtual disk. No growing the disk later then tacking on partitions as the data grows. If I need more space, add a new disk, copy the data, unmount the old, mount the new. Benefits I see of this approach: No possible problems resulting from changing the "physical" disk size. No leftover partitions in the middle of the disk. After a migration, the old disk is still there for an easy rollback. In the event of a problem with the server OS, or for testing, or for an easy upgrade via re-install, you can detach the postgres data disk (or copy it) and attach it to a new server OS install. Tim.
