Jeff,
I'm curious to what kind of testing you've done with LVM. I'm not
currently trying any backup/restore stuff, but I'm running our DBT-2
workload using LVM. I've started collecting vmstat, iostat, and
readprofile data, initially running disktest to gauge the performance.
For anyone curious, I have some data on a 14-disk volume here:
http://developer.osdl.org/markw/lvm/results.4/log/
and a 52-disk volume here:
http://developer.osdl.org/markw/lvm/results.5/data/
Mark
>Jeff <[EMAIL PROTECTED]> writes:
>
> Idea #1:
> Use an LVM and take a snapshop - archive that.
> From the way I see it. the downside is the LVM will use a lot of space
> until the snapshot is removed. Also PG may be in a slightly inconsistant
> state - but this should "appear" to PG the same as if the power went out.
>
> For restore, simply unarchive this snapshot and point postgres at it. Let
> it recover and you are good to go.
>
> Little overhead from what I see...
> I'm leaning towards this method the more I think of it.
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
