On Wed, Jan 26, 2011 at 09:02:24PM -0500, Ray Stell wrote:
On Wed, Jan 26, 2011 at 02:22:41PM -0800, Dan Birken wrote:
Can you give some concrete suggestions on what needs to be added? The
current documentation is here:
It seems like there is a departure in postgresql/pg_hba.conf with
Ben Carbery wrote:
Thanks for the responses all, I have this working now. I had to create a
base backup before copying to the standby for replication to start, but the
main sticking point was actually understanding the terms and concepts
involved..
I think the Binary Replication Tutorial
(I am not the OP, but recently went through the same thing so I'll chime in)
Reading through the documentation now (albeit with a now pretty good
understanding of how everything works), I think the main confusing thing is
how different bits which apply to file-base log shipping, streaming
Dan Birken wrote:
(I am not the OP, but recently went through the same thing so I'll chime in)
Reading through the documentation now (albeit with a now pretty good
understanding of how everything works), I think the main confusing thing is
how different bits which apply to file-base log
On Wed, Jan 26, 2011 at 02:22:41PM -0800, Dan Birken wrote:
Can you give some concrete suggestions on what needs to be added? The
current documentation is here:
http://developer.postgresql.org/pgdocs/postgres/index.html
I had some difficulty getting the keepalives syntax in
Ray Stell wrote:
On Wed, Jan 26, 2011 at 02:22:41PM -0800, Dan Birken wrote:
Can you give some concrete suggestions on what needs to be added? The
current documentation is here:
http://developer.postgresql.org/pgdocs/postgres/index.html
I had some difficulty getting the
On Wed, Jan 26, 2011 at 09:18:01PM -0500, Bruce Momjian wrote:
Uh, the sentence is:
On systems that support the keepalive socket option, setting
tcp_keepalives_idle, tcp_keepalives_interval and tcp_keepalives_count
helps the primary promptly notice a broken connection.
Thanks for the responses all, I have this working now. I had to create a
base backup before copying to the standby for replication to start, but the
main sticking point was actually understanding the terms and concepts
involved..
I think the Binary Replication Tutorial page on the wiki basically
FYI, not looking for a detailed how to here.. I have read the manual twice
and just can't figure which sections are relevant. The manual seems to be
trying to cover all uses simultaneously which is always going to get
confusing :) For example do I need I need WAL archiving or not?
On Tue, Dec 21,
Hi Ben,
On 2010/12/22 7:46, Ben Carbery wrote:
FYI, not looking for a detailed how to here.. I have read the manual twice and
just can't figure which sections are relevant. The manual seems to be trying to
cover all uses simultaneously which is always going to get confusing :) For
example do
Hi Ben,
load balancing is not possible with the tools that are in the postgres
installation. There is no automatic switch-over to a slave if the master
fails. The trigger file needs to be created to make a slave to the master. This
is not done automaitcally by postgres, but should be done by a
On Wed, Dec 22, 2010 at 8:31 AM, Satoshi Nagayasu
satoshi.nagay...@gmail.com wrote:
My blog entry would be a good entry point for you. :)
5 steps to implement a PostgreSQL replication system
http://pgsnaga.blogspot.com/2010/05/5-steps-to-implement-postgresql.html
Or
Hi,
I am having some trouble trying to figure out how to configure this
particular scenario..
I have a pair of pg servers that I want to put in a Master/Standby
configuration. Currently a script dumps the master db every hour, copies it
to the standby, restores, and restarts the server. The aim
13 matches
Mail list logo
