Hi Tom,
I now have excluded ntp as root cause for the CPU cycles being wasted in
user space.
I installed perf and monitored two servers (with different postgresql
versions and hardware specification) which are "hanging" and have some
output. Since I'm no die-hard at interpreting the output of per
Dennis Brouwer writes:
> I now have excluded ntp as root cause for the CPU cycles being wasted in
> user space.
Good, cause that wasn't making any sense at all.
> I installed perf and monitored two servers (with different postgresql
> versions and hardware specification) which are "hanging" and
Is there any way to process WAL logs of an OLTP database for use in a writable,
index heavy, OLAP database? Are there projects out there doing something
similar with the WAL logs?
So far all I've found is Xlogdump and Pglesslog
--
Sent via pgsql-admi
Hi folks, we're snapshotting at san level, two volumes containing a
postgres 9.1.5 database, and pg_xlog respectively.
This database cluster is a streaming replicant.
We're stopping the database completely, taking the snapshots,
restarting the database.
I export these snapshots as luns to a VM, mou
I'm planning my upgrade from 9.1.5 to 9.1.6 on some master and
streaming-replication standby pairs and have some questions:
Generally:
http://www.postgresql.org/docs/9.1/static/warm-standby.html section
25.2.1 says:
"...it is likely that running different minor release levels on primary
and
Hi,
On Tue, 2012-09-25 at 14:22 -0700, Steve Crawford wrote:
> "...it is likely that running different minor release levels on
> primary
> and standby servers will work successfully. However, no formal
> support
> for that is offered and you are advised to keep primary and standby
> servers at
On Wed, Sep 26, 2012 at 3:22 AM, Rick Dicaire wrote:
> Hi folks, we're snapshotting at san level, two volumes containing a
> postgres 9.1.5 database, and pg_xlog respectively.
> This database cluster is a streaming replicant.
> We're stopping the database completely, taking the snapshots,
> restar
> /staging/9.1/main/pg_xlog is really archive directory? restore_command
> should be set to the command which copies the archived WAL files from
> the archive area.
Yes. This is the archive directory.
This begs another question, does a replicant write its own wal files to disk?
--
Sent via pgs
