Optimal Flexible Architecture or Optimal Configuration Layout for Postgres

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

 



I have been looking for a best practices layout for Postgres.

The Centos and Debian distros configure the files for Postgres in different places.  Neither of them seem to put the files in ideal locations for multiple instance administration on the same or different machines.  Has someone already created a best practice for placing pg_xlogs, regular logs, data, indexes, binary code, and configuration files onto the filesystem?

  I would rather use a widely accepted standard than invent one based on one competitors of Postgres.

--
Mark Lehmann
512 689-7705 M

[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