Optimal Flexible Architecture or Optimal Configuration Layout for Postgres

From: Mark Lehmann <mark(dot)lehmann(at)gmail(dot)com>
To: pgsql-admin(at)postgresql(dot)org
Subject: Optimal Flexible Architecture or Optimal Configuration Layout for Postgres
Date: 2009-06-25 14:33:31
Message-ID: 8fa2a6330906250733t6afb0fc7jaa69871e7da0a071@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

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

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Greg Stark 2009-06-25 16:05:13 Fwd: vacuum tx id wraparound issues
Previous Message Kevin Kempter 2009-06-25 14:29:05 Re: vacuum tx id wraparound issues