From: | Shridhar Daithankar <shridhar_daithankar(at)persistent(dot)co(dot)in> |
---|---|
To: | <pgsql-hackers(at)postgresql(dot)org> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: [HACKERS] Physical Database Configuration |
Date: | 2003-06-29 08:56:45 |
Message-ID: | 200306291426.45741.shridhar_daithankar@nospam.persistent.co.in |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
On Wednesday 25 June 2003 21:21, Jonathan Bartlett wrote:
> My solution did not involve tablespaces, but was more of a quick solution
> to make it easier for admins to do _some_ sort of physical configuration.
>
> The idea is that the developer could do something like
>
> 'create alternate location ALTERNATE_LOCATION_NAME for
> DATABASE_OBJECT_NAME at "/PATH/TO/PHYSICAL/FILE";'
>
> We would have a system table holding theses values. Then, all database
> commands which create a file for an object, call open_object(oid,
> object_name) or something to create the file object. This will first look
> in the new system table to see if there is a mapping for an object of this
> name. If so, it will create a symlink to "/PATH/TO/PHYSICAL/FILE" for the
> oid before opening the file.
What you are describing is a subset of tablespace functionality we are
discussing offline. There are few minor differences though.
1. There is no physical file but location would be a directory.
2. The location could also be assigned at the time of object creation.
Otherwise it is exactly what is under consideration..:-)
Shridhar
From | Date | Subject | |
---|---|---|---|
Next Message | Bruno BAGUETTE | 2003-06-29 09:40:41 | Difficulties to do a migration from Oracle8i to PostgreSQL 7.3.3 |
Previous Message | Maksim Likharev | 2003-06-29 08:44:15 | PG crash on simple query |
From | Date | Subject | |
---|---|---|---|
Next Message | Carlos Guzman Alvarez | 2003-06-29 09:53:26 | Re: Getting blocked when receinving response from a Parse |
Previous Message | Dennis Björklund | 2003-06-29 05:40:50 | Re: CVS tip compile failure (was Re: Missing array support) |