Re: Pre-allocation of space: a business rationale

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

 



"Bath, David" <dave.bath@xxxxxxxx> writes:
> C) I want to avoid the possibility of uncontrolled growth of luser data
>    blowing disk leading to stoppage of 24x7 data.

You put the luser data and the critical data into separate tablespaces
that are in separate partitions (filesystems).  End of problem ...

(And no, I don't believe in having Postgres reinvent filesystem-level
functionality.  If you didn't set up appropriate hard partitions,
consider a loopback filesystem for your tablespace.)

			regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

[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