From: Gergely CZUCZY <phoemix@harmless.hu>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: PostgreSQL admin <pgsql-admin@postgresql.org>
Subject: Re: schemas and tablespaces
Date: Fri, 10 Nov 2006 16:38:47 +0100
Message-ID: <20061110153847.GA61907@harmless.hu> (raw)
In-Reply-To: <21191.1163172396@sss.pgh.pa.us>
References: <20061110120522.GA57650@harmless.hu>
<21191.1163172396@sss.pgh.pa.us>
On Fri, Nov 10, 2006 at 10:26:36AM -0500, Tom Lane wrote:
> Gergely CZUCZY <phoemix@harmless.hu> 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.phpAre you planning to re-enable this functionality in the future?
It may worth reconsidering, an other need arised for it by my issue.
Bye,
Gergely Czuczy
mailto: gergely.czuczy@harmless.hu
--
Weenies test. Geniuses solve problems that arise.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: phoemix@harmless.hu, tgl@sss.pgh.pa.us
Subject: Re: schemas and tablespaces
In-Reply-To: <20061110153847.GA61907@harmless.hu>
References: <20061110120522.GA57650@harmless.hu> <21191.1163172396@sss.pgh.pa.us> <20061110153847.GA61907@harmless.hu>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox