Hey, Got the problem again, this time, it is definitely not caused by changes to the filesystem. I think it is more likely because of postgres being run in a virtualized environment. This time, it hung some time after starting a manual analyze on the biggest table so far (55Gb, still growing). Now: Something unusual with this? Regards, panam -- View this message in context: http://postgresql.1045698.n5.nabble.com/Extending-the-volume-size-of-the-data-directory-volume-tp5030663p5135704.html Sent from the PostgreSQL - general mailing list archive at Nabble.com. -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
