![]() If wal_keep_segments is a high enough number to retain the WAL # Enable WAL archiving on the primary to an archive directory accessible from # archiving to an archive directory accessible from the standby, this may # online-backup and the startup of streaming replication. # larger than the number of segments generated between the beginning of # the standby server before shipping them, set the minimum number of segments # To prevent the primary server from removing the WAL segments required for # Set the maximum number of concurrent connections from the standby servers. But you can choose "archive" if you never connect to the ![]() # To enable read-only queries on a standby server, wal_level must be set to Set up the streaming replication related parameters on the primary server. # The standby server must connect with a user that has replication privileges. Set up connections and authentication on the primary so that the standby server can successfully connect to the replication pseudo-database on the primary. $ CREATE ROLE replication WITH REPLICATION PASSWORD 'password' LOGIN Create an user named replication with REPLICATION privileges. Create the initial database cluster in the primary server as usual, using initdb. This requires only configure, make and make install. Install postgres in the primary and standby server as usual. NB: there is overlap between this section and Binary Replication Tutorial
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |