X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 5FC023B477D for ; Wed, 15 Dec 2004 15:40:53 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 72802-09 for ; Wed, 15 Dec 2004 15:40:46 +0000 (GMT) Received: from netexch02.netservices.eng.net (mailhost.netservices.eng.net [213.130.128.196]) by svr1.postgresql.org (Postfix) with ESMTP id F147D3B475A for ; Wed, 15 Dec 2004 15:40:48 +0000 (GMT) Received: by NETEXCH02 with Internet Mail Service (5.5.2653.19) id <4TDKNF2J>; Wed, 15 Dec 2004 15:40:47 -0000 Message-ID: <99795FEF570BA64EA0FA6D4540FBB04001191C04@NETEXCH02> From: Sam Mortimer To: "'pgsql-admin@postgresql.org'" Subject: robust way of moving tables to a different disk?? Date: Wed, 15 Dec 2004 15:40:41 -0000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.374 tagged_above=0 required=5 tests=DNS_FROM_RFC_ABUSE X-Spam-Level: X-Archive-Number: 200412/189 X-Sequence-Number: 15775 Hello, I'd like to move some tables from a particular database onto a different set of disks. However, I can't see any robust way of achieving this. I've tried using symlinks but these can easily be broken by a mixture of "vacuum full" and growing the table again (assuming the table is large enough to span multiple files). We can handle a solution that breaks when the table is dropped and recreated, that's a special enough case enough to be managed. Any ideas welcome! Regards, -Sam.