Received: from localhost (uranus.hub.org [200.46.204.60]) by postgresql.org (Postfix) with ESMTP id 6A4449FB2F1 for ; Fri, 10 Nov 2006 11:26:47 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.60]) (amavisd-new, port 10024) with ESMTP id 85442-04 for ; Fri, 10 Nov 2006 11:26:44 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 30B649FA3A7 for ; Fri, 10 Nov 2006 11:26:40 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id kAAFQaEa021192; Fri, 10 Nov 2006 10:26:36 -0500 (EST) To: Gergely CZUCZY cc: PostgreSQL admin Subject: Re: schemas and tablespaces In-reply-to: <20061110120522.GA57650@harmless.hu> References: <20061110120522.GA57650@harmless.hu> Comments: In-reply-to Gergely CZUCZY message dated "Fri, 10 Nov 2006 13:05:22 +0100" Date: Fri, 10 Nov 2006 10:26:36 -0500 Message-ID: <21191.1163172396@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200611/105 X-Sequence-Number: 23632 Gergely CZUCZY writes: > For this i had the idea to put all projects into > separate tablespaces by their schemas at the next > upgrade. But as i check the current documentation > there were no such feature that all of a schema's > sub-elements can be put into a tablespace. Nope. The original tablespace patch actually did have the notion of a default tablespace associated with a schema, but we took it out after a little experience with the patch. See very long thread http://archives.postgresql.org/pgsql-hackers/2004-10/msg00583.php regards, tom lane