Re: Multiple Tablespaces with single mount point?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxx> wrote:
Thank you. I was referring to this link and that's what made me think, what if in the future scenario.


On Fri, Aug 12, 2016 at 2:07 PM, David G. Johnston <david.g.johnston@xxxxxxxxx> wrote:
On Fri, Aug 12, 2016 at 4:59 PM, Curious Tech <cutech777@xxxxxxxxx> 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.




[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]

  Powered by Linux