From: | Curious Tech <cutech777(at)gmail(dot)com> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Multiple Tablespaces with single mount point? |
Date: | 2016-08-12 21:14:28 |
Message-ID: | CAHZiM6Q8kA3ojoBj9jatyr4=_aSrWhUfo6eBoyGFPq3F6_BahA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Thank you. I was referring to this link and that's what made me think, what
if in the future scenario.
https://wiki.postgresql.org/wiki/Simple_Configuration_Recommendation
On Fri, Aug 12, 2016 at 2:07 PM, David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
> On Fri, Aug 12, 2016 at 4:59 PM, Curious Tech <cutech777(at)gmail(dot)com> wrote:
>
>> Hello,
>>
>> I want to know what is the general practice when only one mount point is
>> available.
>>
>> 1. Use default tablespace
>> 2. Use Default + User Define one tablespace
>> 3. Use Default + User Defined Data + User Defined Index tablespaces
>>
>>
> 1.
>
> Using non-default tablespace adds backup/restore complications. Don't do
> that without a demonstrable benefit. You will not be able to demonstrate a
> benefit when you only have a single filesystem.
>
> David J.
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Curious Tech | 2016-08-12 21:21:35 | Re: Multiple Tablespaces with single mount point? |
Previous Message | David G. Johnston | 2016-08-12 21:07:24 | Re: Multiple Tablespaces with single mount point? |