From: Tom Lane <tgl@sss.pgh.pa.us>
To: Campbell, Lance <lance@illinois.edu>
Cc: pgsql-performance@postgresql.org
Subject: Re: Symbolic Links to Tablespaces
Date: Mon, 26 May 2008 11:08:51 -0400
Message-ID: <21505.1211814531@sss.pgh.pa.us> (raw)
In-Reply-To: <B10E6810AC2A2F4EA7550D072CDE8760CDDD7B@SAB-FENWICK.sab.uiuc.edu>
References: <B10E6810AC2A2F4EA7550D072CDE8760CDDD7B@SAB-FENWICK.sab.uiuc.edu>
"Campbell, Lance" <lance@illinois.edu> writes:
> I have started to define tablespaces on different disks. Is there any
> performance issues related to referencing tablespaces on different disks
> with symbolic links? By using symbolic links to tablespaces can I then
> stop the database and move a particular tablespace from one location to
> another without causing a problem? This would seem to give a lot of
> flexibility to the location of tablespaces.
A tablespace already is a symbolic link --- read
http://www.postgresql.org/docs/8.2/static/storage.html
Putting another one into the path will eat cycles and doesn't seem like
it could buy anything.
regards, tom lane
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 using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, lance@illinois.edu
Subject: Re: Symbolic Links to Tablespaces
In-Reply-To: <21505.1211814531@sss.pgh.pa.us>
* 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