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 98B273B6B93 for ; Thu, 16 Dec 2004 10:07:02 +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 84803-09 for ; Thu, 16 Dec 2004 10:06:53 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.199]) by svr1.postgresql.org (Postfix) with ESMTP id DA2CB3B6B65 for ; Thu, 16 Dec 2004 10:06:54 +0000 (GMT) Received: by rproxy.gmail.com with SMTP id c16so1960643rne for ; Thu, 16 Dec 2004 02:06:55 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=maG4CG8YfN0jNNkEiDpRDsvDJ8cNV13gjnYTyHjoTKKZ6WLT0wGvulH/NrHXcCWCJnGucSdDAs9qk3UjrHXpRhuIgG6QMWXXR/wbtimTS+A5w8BQa+D7DYBGi5xWygran3J0y/zrtiVz1kUhNovkUOc0rCNKgkRHMbicjVL/vIo= Received: by 10.38.76.69 with SMTP id y69mr2482882rna; Thu, 16 Dec 2004 02:06:54 -0800 (PST) Received: by 10.38.149.60 with HTTP; Thu, 16 Dec 2004 02:06:54 -0800 (PST) Message-ID: Date: Thu, 16 Dec 2004 10:06:54 +0000 From: Sam Mortimer Reply-To: Sam Mortimer To: pgsql-admin@postgresql.org Subject: robust way of moving tables to a different disk?? Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.024 tagged_above=0 required=5 tests=RCVD_BY_IP X-Spam-Level: X-Archive-Number: 200412/156 X-Sequence-Number: 15742 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.