Re: pg_upgrade & tablespaces

From: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
To: Joseph Kregloh <jkregloh(at)sproutloud(dot)com>
Cc: Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com>, John R Pierce <pierce(at)hogranch(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: pg_upgrade & tablespaces
Date: 2013-12-27 22:52:29
Message-ID: CAMkU=1x_XNcx+E1xcctPocFMSEPGdaZFWzf6yzxeOo9KXGYBWw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

On Friday, December 27, 2013, Joseph Kregloh wrote:

> FYI, some testing showed that playing around with spclocation in
>> pg_tablespace is not recommended.
>
>
> Do you happen to have more information about this? Because it would
> actually solve all my problems by moving the user created tablespaces out
> of the /data directory. But I would like more information on the subject
> before even thinking about it anymore. I did it a couple times for testing
> purposes. I modified the spclocation in pg_tablespace and then move the
> folder.
>

spclocation no longer exists in 9.3. If the database needs to know where
the location is, it inspects the symlink in pg_tblspc to figure that out.

Cheers,

Jeff

>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2013-12-28 00:10:25 Re: pg_upgrade & tablespaces
Previous Message Adrian Klaver 2013-12-27 22:34:52 Re: pg_upgrade & tablespaces

Browse pgsql-hackers by date

  From Date Subject
Next Message MauMau 2013-12-27 23:04:09 Re: [bug fix] ECPG app crashes due to SIGBUS on SPARC Solaris
Previous Message Adrian Klaver 2013-12-27 22:34:52 Re: pg_upgrade & tablespaces