From: Enrico Weigelt <weigelt@metux.de>
To: pgsql-admin@postgresql.org
Subject: Re: linux standard layout
Date: Sat, 1 May 2010 18:49:05 +0200
Message-ID: <20100501164905.GC24971@nibiru.local> (raw)
In-Reply-To: <Pine.GSO.4.64.1003082243200.10671@coe.tamu.edu>
References: <Pine.GSO.4.64.1003082243200.10671@coe.tamu.edu>
* Ben Kim <bkim@tamu.edu> wrote:
Hi,
> I don't like the VMWare environment, but it's not my choice, and assuming
> the cpu load is ok, will there be any benefits if I put each database on
> separate partitions, vs. simply using the one data directory?
Depending on your underlying storage, it might be advisable to put
each instance on an separate spindle/enclosure, maybe even on an
different bus. But there's no universal answer to this.
You could start putting each instance on an separate partition or
lvm volume, record your real disk workload w/ blktrace and try it
out on different storage configurations w/ blkreplay.
> Also, how is using standard rpm, with its standard layout (/var/lib/pgsql,
> /usr/lib/pgsql, ...), generally regarded?
When working w/ some mainline distribution, always try to use that
distro's packages (not distro-independent binpkgs!), unless you've
got a valid reason for doing otherwise. When building your own
packages, use your distro's build machinery for that.
If your (virtual) box really only runs the server and you'd like to
do specific optimizations (eg. processor specific, etc), you could
create your own micro-distro. I've got some tools to ease that -
just mail me directly if you're interested.
> I have someone who opposes the use of standard rpms (even yums) for this
> reason. I thought I'd check out how it is received professionally.
Well, that depends on his specific reasons. For examples, several
distros tend to do strange things, you might not want in your
environment. Perhaps you need certain patches your distro doenst
provide. But even in this case you should try to use your distro's
build machinery for creating your own package.
Please ask your collegue for his concrete reasons and report back :)
> If I compile something from the source, sometimes I see a boundary
> condition - like, if I already have DBI from a standard rpm, it expects
> postgresql library at a certain location - making me wonder whether I
> should remove the DBI rpm and compile it also from the source, or whether
> I should use standard rpms for postgresql as well. (DBI may not be a good
> example.)
Pathes should be configurable, or you could use symlinks or bind mounts.
cu
--
---------------------------------------------------------------------
Enrico Weigelt == metux IT service - http://www.metux.de/
---------------------------------------------------------------------
Please visit the OpenSource QM Taskforce:
http://wiki.metux.de/public/OpenSource_QM_Taskforce
Patches / Fixes for a lot dozens of packages in dozens of versions:
http://patches.metux.de/
---------------------------------------------------------------------
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: weigelt@metux.de
Subject: Re: linux standard layout
In-Reply-To: <20100501164905.GC24971@nibiru.local>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox