I send a nightly dump of my production database to a development server. A
script drops the existing development database and replaces it with the
current production copy.
Each dev uses her own copy of the database. Is there a way to copy the
current development database to a differently named db
Newb question here. I have streaming replication working with 9.2 and I'm
using Bucardo's check_postgres.pl to monitor replication. I see that it
runs this query on the slave:
SELECT pg_last_xlog_receive_location() AS receive,
pg_last_xlog_replay_location() AS replay
That returns hex, which is th
Hit send on that one too soon. I see 6.5k access share locks out of 7.5k
transactions.
On Tue, Nov 26, 2013 at 12:41 PM, wrote:
> I have a 9.2 server that occasionally becomes CPU bound. Disk wait is
> nominal and there's no memory pressure. The workload is almost all reads
> and the cache hit
I have a 9.2 server that occasionally becomes CPU bound. Disk wait is
nominal and there's no memory pressure. The workload is almost all reads
and the cache hit rate is high.
For some one minute periods, my monitoring shows around 1.5k to 2k access
share locks out of a total of 7.5 to 8k transacti
Thank you for the answers. I'm still confused. If fsync is not replicated
to the slave, then how is replication affected by a corrupt master? If the
master dies and there's a commit recorded in the wal log that didn't
actually happen, wouldn't the slave still be expected to be in a sane
state, with
Newb question.
I'm running 9.1 with a slave using streaming replication. A coworker wants
to turn off fsync on the master and insists that the slave will still be in
a usable state if there is a failure on the master. We all know that
turning off fsync is a bad idea, but I was under the impression
