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:21:35 |
Message-ID: | CAHZiM6QO6d0b9nVUpRGMEO2AB_NDsP0R+ftOFmgzVQCPZiMxgA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Even otherwise, is the general recommendation is to store the data and xlog
on different volumes a preferred way?
Thank you.
On Fri, Aug 12, 2016 at 2:14 PM, Curious Tech <cutech777(at)gmail(dot)com> wrote:
> 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 | David G. Johnston | 2016-08-12 21:48:50 | Re: Multiple Tablespaces with single mount point? |
Previous Message | Curious Tech | 2016-08-12 21:14:28 | Re: Multiple Tablespaces with single mount point? |