PostgreSQL 9.3 Allow a streaming replication standby to follow a timeline switch

最新推荐文章于 2024-09-26 13:44:28 发布
最新推荐文章于 2024-09-26 13:44:28 发布
阅读量166 收藏
点赞数
文章标签： git 数据库
原文链接：https://yq.aliyun.com/articles/14673
版权 
Allow a streaming replication standby to follow a timeline switch.

Before this patch, streaming replication would refuse to start replicating
if the timeline in the primary doesn't exactly match the standby. The
situation where it doesn't match is when you have a master, and two
standbys, and you promote one of the standbys to become new master.
Promoting bumps up the timeline ID, and after that bump, the other standby
would refuse to continue.

There's significantly more timeline related logic in streaming replication
now. First of all, when a standby connects to primary, it will ask the
primary for any timeline history files that are missing from the standby.
The missing files are sent using a new replication command TIMELINE_HISTORY,
and stored in standby's pg_xlog directory. Using the timeline history files,
the standby can follow the latest timeline present in the primary
(recovery_target_timeline='latest'), just as it can follow new timelines
appearing in an archive directory.

START_REPLICATION now takes a TIMELINE parameter, to specify exactly which
timeline to stream WAL from. This allows the standby to request the primary
to send over WAL that precedes the promotion. The replication protocol is
changed slightly (in a backwards-compatible way although there's little hope
of streaming replication working across major versions anyway), to allow
replication to stop when the end of timeline reached, putting the walsender
back into accepting a replication command.

Many thanks to Amit Kapila for testing and reviewing various versions of
this patch.

PostgreSQL 9.3 对流复制协议进行了修改, 实现了通过流复制协议实现时间线文件的复制. 非常适合用在角色切换以及多standby的环境.
以前流复制协议并不支持复制时间线文件, 所以每当切换角色后, 都需要手工复制这个文件到standby中.
具体的实现见本文参考部分.

[测试]
一. PostgreSQL 9.2 : 
1.建立standby
主库参数 : 
$PGDATA : /pgdata1919
no other tablespace.

postgresql.conf
 
listen_addresses = '0.0.0.0'            # what IP address(es) to listen on;
port = 1919                             # (change requires restart)
max_connections = 100                   # (change requires restart)
superuser_reserved_connections = 13     # (change requires restart)
unix_socket_directory = '.'             # (change requires restart)
unix_socket_permissions = 0700          # begin with 0 to use octal notation
shared_buffers = 1024MB                 # min 128kB
maintenance_work_mem = 512MB            # min 1MB
wal_level = hot_standby                 # minimal, archive, or hot_standby
synchronous_commit = off                # synchronization level;
wal_sync_method = fdatasync             # the default is the first option
wal_buffers = 16384kB                   # min 32kB, -1 sets based on shared_buffers
wal_writer_delay = 10ms         # 1-10000 milliseconds
checkpoint_segments = 32                # in logfile segments, min 1, 16MB each
archive_mode = on               # allows archiving to be done
archive_command = '/bin/date'           # command to use to archive a logfile segment
max_wal_senders = 32            # max number of walsender processes
wal_keep_segments = 64          # in logfile segments, 16MB each; 0 disables
hot_standby = on                        # "on" allows queries during recovery
max_standby_archive_delay = 300s        # max delay before canceling queries
max_standby_streaming_delay = 300s      # max delay before canceling queries
wal_receiver_status_interval = 1s       # send replies at least this often
hot_standby_feedback = on               # send info from standby to prevent
random_page_cost = 2.0                  # same scale as above
effective_cache_size = 8192MB
log_destination = 'csvlog'              # Valid values are combinations of
logging_collector = on          # Enable capturing of stderr and csvlog
log_directory = 'pg_log'                # directory where log files are written,
log_filename = 'postgresql-%Y-%m-%d_%H%M%S.log' # log file name pattern,
log_file_mode = 0600                    # creation mode for log files,
log_truncate_on_rotation = on           # If on, an existing log file with the
log_rotation_age = 1d                   # Automatic rotation of logfiles will
log_rotation_size = 10MB                # Automatic rotation of logfiles will
log_checkpoints = on
log_connections = on
log_disconnections = on
log_error_verbosity = verbose           # terse, default, or verbose messages
log_timezone = 'PRC'
autovacuum = on                 # Enable autovacuum subprocess?  'on'
datestyle = 'iso, mdy'
timezone = 'PRC'
lc_messages = 'C'                       # locale for system error message
lc_monetary = 'C'                       # locale for monetary formatting
lc_numeric = 'C'                        # locale for number formatting
lc_time = 'C'                           # locale for time formatting
default_text_search_config = 'pg_catalog.english'
standard_conforming_strings = off


recovery.done
 
recovery_target_timeline = 'latest'
standby_mode = on
primary_conninfo = 'host=127.0.0.1 port=11919 user=postgres keepalives_idle=60'         # e.g. 'host=localhost port=5432'

pg_hba.conf
 
local   all             all                                     trust
host    all             all             127.0.0.1/32            trust
host    all             all             ::1/128                 trust
local   replication     postgres                                trust
host    replication     postgres        127.0.0.1/32            trust
host all all 0.0.0.0/0 md5


备库参数 : 
 
$PGDATA : /pgdata11919
no other tablespace.


postgresql.conf
 
port = 11919                             # (change requires restart)
# 其他与primary配置相同

recovery.conf
 
recovery_target_timeline = 'latest'
standby_mode = on
primary_conninfo = 'host=127.0.0.1 port=1919 user=postgres keepalives_idle=60'         # e.g. 'host=localhost port=5432'

pg_hba.conf
 
local   all             all                                     trust
host    all             all             127.0.0.1/32            trust
host    all             all             ::1/128                 trust
local   replication     postgres                                trust
host    replication     postgres        127.0.0.1/32            trust
host all all 0.0.0.0/0 md5


启动主库和备库后, 确定正常复制.
pg_ctl start -D /pgdata1919
pg_ctl start -D /pgdata11919
ps -ewf|grep pg92 
pg92     11644     1  0 15:27 pts/1    00:00:00 /opt/pgsql9.2.4/bin/postgres
pg92     11645 11644  0 15:27 ?        00:00:00 postgres: logger process    
pg92     11647 11644  0 15:27 ?        00:00:00 postgres: checkpointer process   
pg92     11648 11644  0 15:27 ?        00:00:00 postgres: writer process    
pg92     11649 11644  0 15:27 ?        00:00:00 postgres: wal writer process   
pg92     11650 11644  0 15:27 ?        00:00:00 postgres: autovacuum launcher process   
pg92     11651 11644  0 15:27 ?        00:00:00 postgres: archiver process   
pg92     11652 11644  0 15:27 ?        00:00:00 postgres: stats collector process   
pg92     11658     1  0 15:27 pts/1    00:00:00 /opt/pgsql9.2.4/bin/postgres -D /pgdata11919
pg92     11659 11658  0 15:27 ?        00:00:00 postgres: logger process                    
pg92     11660 11658  0 15:27 ?        00:00:00 postgres: startup process   recovering 0000000100000001000000A1
pg92     11661 11658  0 15:27 ?        00:00:00 postgres: checkpointer process              
pg92     11662 11658  0 15:27 ?        00:00:00 postgres: writer process                    
pg92     11663 11658  0 15:27 ?        00:00:00 postgres: stats collector process           
pg92     11729 11658  0 15:28 ?        00:00:00 postgres: wal receiver process   streaming 1/A10245E0
pg92     11730 11644  0 15:28 ?        00:00:00 postgres: wal sender process postgres 127.0.0.1(61278) streaming 1/A10245E0


2.正常关闭primary
 
pg_ctl stop -m fast -D /pgdata1919


3.promote standby
 
pg92@db-172-16-3-33-> pg_ctl promote -D /pgdata11919
server promoting

4.将primary改成standby启动
 
pg92@db-172-16-3-33-> cd /pgdata1919
pg92@db-172-16-3-33-> mv recovery.done recovery.conf
pg92@db-172-16-3-33-> pg_ctl start -D /pgdata1919
server starting

查看日志
 
cd /pgdata1919/pg_log
2013-05-08 15:32:05.887 CST,,,11840,,5189ff75.2e40,1,,2013-05-08 15:32:05 CST,,0,FATAL,XX000,"timeline 2 of the primary does not match recovery target timeline 1",,,,,,,,"libpqrcv_connect, libpqwalreceiver.c:154",""

需要手工将时间线文件拷贝到pg_xlog中.
 
pg92@db-172-16-3-33-> cp /pgdata11919/pg_xlog/00000002.history /pgdata1919/pg_xlog/

再次查看日志, 正常复制
 
2013-05-08 15:33:20.884 CST,,,11763,,5189ff39.2df3,5,,2013-05-08 15:31:05 CST,1/0,0,LOG,00000,"new target timeline is 2",,,,,,,,"rescanLatestTimeLine, xlog.c:4644",""
2013-05-08 15:33:21.177 CST,,,11876,,5189ffc0.2e64,1,,2013-05-08 15:33:20 CST,,0,LOG,00000,"streaming replication successfully connected to primary",,,,,,,,"libpqrcv_connect, libpqwalreceiver.c:171",""
2013-05-08 15:33:21.372 CST,,,11763,,5189ff39.2df3,6,,2013-05-08 15:31:05 CST,1/0,0,LOG,00000,"redo starts at 1/A2000080",,,,,,,,"StartupXLOG, xlog.c:6817",""


二. PostgreSQL 9.3 : 
1.建立standby
主库参数 : 
$PGDATA : /pgdata1999
no other tablespace.

postgresql.conf
 
listen_addresses = '0.0.0.0'            # what IP address(es) to listen on;
port = 1999                             # (change requires restart)
max_connections = 100                   # (change requires restart)
superuser_reserved_connections = 13     # (change requires restart)
unix_socket_directories = '.'   # comma-separated list of directories
unix_socket_permissions = 0700          # begin with 0 to use octal notation
tcp_keepalives_idle = 60                # TCP_KEEPIDLE, in seconds;
tcp_keepalives_interval = 60            # TCP_KEEPINTVL, in seconds;
tcp_keepalives_count = 60               # TCP_KEEPCNT;
shared_buffers = 1024MB                 # min 128kB
maintenance_work_mem = 512MB            # min 1MB
max_stack_depth = 8MB                   # min 100kB
wal_level = hot_standby                 # minimal, archive, or hot_standby
synchronous_commit = off                # synchronization level;
wal_sync_method = fdatasync             # the default is the first option
wal_buffers = 16384kB                   # min 32kB, -1 sets based on shared_buffers
wal_writer_delay = 10ms         # 1-10000 milliseconds
commit_delay = 10                       # range 0-100000, in microseconds
commit_siblings = 5                     # range 1-1000
checkpoint_segments = 32                # in logfile segments, min 1, 16MB each
archive_mode = on               # allows archiving to be done
archive_command = '/bin/date'           # command to use to archive a logfile segment
max_wal_senders = 32            # max number of walsender processes
wal_keep_segments = 64          # in logfile segments, 16MB each; 0 disables
hot_standby = on                        # "on" allows queries during recovery
max_standby_archive_delay = 300s        # max delay before canceling queries
max_standby_streaming_delay = 300s      # max delay before canceling queries
wal_receiver_status_interval = 1s       # send replies at least this often
hot_standby_feedback = on               # send info from standby to prevent
random_page_cost = 2.0                  # same scale as above
effective_cache_size = 8192MB
log_destination = 'csvlog'              # Valid values are combinations of
logging_collector = on          # Enable capturing of stderr and csvlog
log_directory = 'pg_log'                # directory where log files are written,
log_filename = 'postgresql-%Y-%m-%d_%H%M%S.log' # log file name pattern,
log_file_mode = 0600                    # creation mode for log files,
log_truncate_on_rotation = on           # If on, an existing log file with the
log_rotation_age = 1d                   # Automatic rotation of logfiles will
log_rotation_size = 10MB                # Automatic rotation of logfiles will
client_min_messages = notice            # values in order of decreasing detail:
log_checkpoints = on
log_connections = on
log_disconnections = on
log_error_verbosity = verbose           # terse, default, or verbose messages
log_timezone = 'PRC'
autovacuum = on                 # Enable autovacuum subprocess?  'on'
datestyle = 'iso, mdy'
timezone = 'PRC'
lc_messages = 'en_US.utf8'                      # locale for system error message
lc_monetary = 'en_US.utf8'                      # locale for monetary formatting
lc_numeric = 'en_US.utf8'                       # locale for number formatting
lc_time = 'en_US.utf8'                          # locale for time formatting
default_text_search_config = 'pg_catalog.english'

recovery.done
 
recovery_target_timeline = 'latest'
standby_mode = on
primary_conninfo = 'host=127.0.0.1 port=11999 user=postgres keepalives_idle=60'         # e.g. 'host=localhost port=5432'

pg_hba.conf
 
local   all             all                                     trust
host    all             all             127.0.0.1/32            trust
host    all             all             ::1/128                 trust
local   replication     postgres                                trust
host    replication     postgres        127.0.0.1/32            trust
host all all 0.0.0.0/0 md5


备库参数 : 
 
$PGDATA : /pgdata11999
no other tablespace.

postgresql.conf
 
port = 11999                             # (change requires restart)
# 其他与primary配置相同

recovery.conf
 
recovery_target_timeline = 'latest'
standby_mode = on
primary_conninfo = 'host=127.0.0.1 port=1999 user=postgres keepalives_idle=60'          # e.g. 'host=localhost port=5432'

pg_hba.conf
 
local   all             all                                     trust
host    all             all             127.0.0.1/32            trust
host    all             all             ::1/128                 trust
local   replication     postgres                                trust
host    replication     postgres        127.0.0.1/32            trust
host all all 0.0.0.0/0 md5

启动主库和备库后, 确定正常复制.
pg_ctl start -D /pgdata1999
pg_ctl start -D /pgdata11999
ps -ewf|grep pg93 
pg93     12122     1  0 15:39 pts/1    00:00:00 /opt/pgsql9.3/bin/postgres
pg93     12123 12122  0 15:39 ?        00:00:00 postgres: logger process   
pg93     12125 12122  0 15:39 ?        00:00:00 postgres: checkpointer process   
pg93     12126 12122  0 15:39 ?        00:00:00 postgres: writer process   
pg93     12127 12122  0 15:39 ?        00:00:00 postgres: wal writer process   
pg93     12128 12122  0 15:39 ?        00:00:00 postgres: autovacuum launcher process   
pg93     12129 12122  0 15:39 ?        00:00:00 postgres: archiver process   
pg93     12130 12122  0 15:39 ?        00:00:00 postgres: stats collector process   
pg93     12135     1  0 15:39 pts/1    00:00:00 /opt/pgsql9.3/bin/postgres -D /pgdata11999
pg93     12136 12135  0 15:39 ?        00:00:00 postgres: logger process                  
pg93     12137 12135  0 15:39 ?        00:00:00 postgres: startup process   recovering 000000010000000200000050
pg93     12138 12135  0 15:39 ?        00:00:00 postgres: checkpointer process            
pg93     12139 12135  0 15:39 ?        00:00:00 postgres: writer process                  
pg93     12140 12135  0 15:39 ?        00:00:00 postgres: stats collector process         
pg93     12141 12135  0 15:39 ?        00:00:00 postgres: wal receiver process            
pg93     12142 12122  0 15:39 ?        00:00:00 postgres: wal sender process postgres 127.0.0.1(9639) streaming 2/50000090

2.正常关闭primary
 
pg93@db-172-16-3-33-> pg_ctl stop -m fast -D /pgdata1999
waiting for server to shut down.... done
server stopped

3.promote standby
 
pg93@db-172-16-3-33-> pg_ctl promote -D /pgdata11999
server promoting

4.将primary改成standby启动
 
pg93@db-172-16-3-33-> cd /pgdata1999
pg93@db-172-16-3-33-> mv recovery.done recovery.conf
pg93@db-172-16-3-33-> pg_ctl start
server starting

查看日志, 时间线文件已经自动获取了.
 
pg93@db-172-16-3-33-> cd pg_log
2013-05-08 15:43:07.089 CST,,,12196,,518a020b.2fa4,1,,2013-05-08 15:43:07 CST,,0,LOG,00000,"database system was shut down at 2013-05-08 15:42:38 CST",,,,,,,,"StartupXLOG, xlog.c:4885",""
2013-05-08 15:43:07.089 CST,,,12196,,518a020b.2fa4,2,,2013-05-08 15:43:07 CST,,0,LOG,00000,"entering standby mode",,,,,,,,"StartupXLOG, xlog.c:4958",""
2013-05-08 15:43:07.098 CST,,,12196,,518a020b.2fa4,3,,2013-05-08 15:43:07 CST,1/0,0,LOG,00000,"consistent recovery state reached at 2/51000090",,,,,,,,"CheckRecoveryConsistency, xlog.c:6175",""
2013-05-08 15:43:07.098 CST,,,12196,,518a020b.2fa4,4,,2013-05-08 15:43:07 CST,1/0,0,LOG,00000,"record with zero length at 2/51000090",,,,,,,,"ReadRecord, xlog.c:3283",""
2013-05-08 15:43:07.099 CST,,,12194,,518a020a.2fa2,1,,2013-05-08 15:43:06 CST,,0,LOG,00000,"database system is ready to accept read only connections",,,,,,,,"sigusr1_handler, postmaster.c:4656",""
2013-05-08 15:43:07.102 CST,,,12200,,518a020b.2fa8,1,,2013-05-08 15:43:07 CST,,0,LOG,00000,"fetching timeline history file for timeline 2 from primary server",,,,,,,,"WalRcvFetchTimeLineHistoryFiles, walreceiver.c:660",""
2013-05-08 15:43:07.128 CST,,,12200,,518a020b.2fa8,2,,2013-05-08 15:43:07 CST,,0,LOG,00000,"started streaming WAL from primary at 2/51000000 on timeline 1",,,,,,,,"WalReceiverMain, walreceiver.c:365",""
2013-05-08 15:43:07.128 CST,,,12200,,518a020b.2fa8,3,,2013-05-08 15:43:07 CST,,0,LOG,00000,"replication terminated by primary server","End of WAL reached on timeline 1 at 2/51000090",,,,,,,"WalReceiverMain, walreceiver.c:438",""
2013-05-08 15:43:07.128 CST,,,12196,,518a020b.2fa4,5,,2013-05-08 15:43:07 CST,1/0,0,LOG,00000,"new target timeline is 2",,,,,,,,"rescanLatestTimeLine, xlog.c:3455",""
2013-05-08 15:43:07.128 CST,,,12200,,518a020b.2fa8,4,,2013-05-08 15:43:07 CST,,0,LOG,00000,"restarted WAL streaming at 2/51000000 on timeline 2",,,,,,,,"WalReceiverMain, walreceiver.c:370",""
2013-05-08 15:43:07.303 CST,,,12196,,518a020b.2fa4,6,,2013-05-08 15:43:07 CST,1/0,0,LOG,00000,"redo starts at 2/51000090",,,,,,,,"StartupXLOG, xlog.c:5524",""

数据库进程正常
 
pg93     12135     1  0 15:39 pts/1    00:00:00 /opt/pgsql9.3/bin/postgres -D /pgdata11999
pg93     12136 12135  0 15:39 ?        00:00:00 postgres: logger process                  
pg93     12138 12135  0 15:39 ?        00:00:00 postgres: checkpointer process            
pg93     12139 12135  0 15:39 ?        00:00:00 postgres: writer process                  
pg93     12140 12135  0 15:39 ?        00:00:00 postgres: stats collector process         
pg93     12179 12135  0 15:42 ?        00:00:00 postgres: wal writer process              
pg93     12180 12135  0 15:42 ?        00:00:00 postgres: autovacuum launcher process     
pg93     12181 12135  0 15:42 ?        00:00:00 postgres: archiver process   last was 00000002.history
pg93     12194     1  0 15:43 pts/1    00:00:00 /opt/pgsql9.3/bin/postgres
pg93     12195 12194  0 15:43 ?        00:00:00 postgres: logger process   
pg93     12196 12194  0 15:43 ?        00:00:00 postgres: startup process   recovering 000000020000000200000051
pg93     12197 12194  0 15:43 ?        00:00:00 postgres: checkpointer process   
pg93     12198 12194  0 15:43 ?        00:00:00 postgres: writer process   
pg93     12199 12194  0 15:43 ?        00:00:00 postgres: stats collector process   
pg93     12200 12194  0 15:43 ?        00:00:00 postgres: wal receiver process   streaming 2/5100EC10
pg93     12201 12135  0 15:43 ?        00:00:00 postgres: wal sender process postgres 127.0.0.1(61597) streaming 2/5100EC10
pg93     12211 12135  0 15:43 ?        00:00:00 postgres: autovacuum worker process   postgres


[参考]
流复制协议新增了TIMELINE_HISTORY 命令, 同时对START_REPLICATION命令做了修改支持TIMELINE参数. 
TIMELINE_HISTORY tli
Requests the server to send over the timeline history file for timeline tli. Server replies with a result set of a single row, containing two fields:

filename
Filename of the timeline history file, e.g 00000002.history.

content
Contents of the timeline history file.

START_REPLICATION XXX/XXX TIMELINE tli

3. src/backend/replication/walreceiver.c
 
+           ereport(LOG,
+                   (errmsg("fetching timeline history file for timeline %u from primary server",
+                           tli)));

weixin_34321753
关注
postgresql主从备份_Postgresql数据库主从流复制
weixin_39532628的博客
01-28 328
由于某个项目前期资源紧张，使用的Postgresql单节点数据库；为解决项目数据库安全性问题，小蜗牛应要求整理Postgresql数据库主从高可用方案，以下操作为部署主从流复制测试过程，后续整理pgpool高可用、负载均衡方案。。一、安装依赖yum install -y gcc-c++ zlib-devel vim openssh-clients二、安装PGtar zxvf postgresql-...
postgresql主从备份_postgresql 主从复制并切换
weixin_42513616的博客
01-28 831
1 环境192.168.19.145 Kylin 3.3 mysqlhq 9.5.2 psql_master192.168.19.227 Kylin 3.3 mysql3 9.5.2 psql_standbypostgres=# select version();version-----------------------------------------------------...
postgresql 流复制协议走读
04-19 865
笔者使用 Stolon Cluster 实现 PostgreSQL10 数据库的高可用。本文将按照笔者的理解，梳理 Stolon 以及 Postgres 高可用实现逻辑。 Postgres 流复制协议 Stolon 利用 Postgres 9.0+ 以上版本提供的流复制特性，实现了高可用的功能。在 Postgres10 中，Stolon 通过管理 postgresql.conf、 recovery.conf这些文件，影响 postgres 角色、行为。Stolon 在备用服务器，根据集群配置生成 recov
PostgreSQL主机无法自动清理pg_wal下wal文件
m0_37535673的博客
01-14 4016
数据库数据目录下pg_wal的WAL文件在开启归档的模式下会将已归档WAL文件自动清理，具体流程是，转储WAL段文件到disk，写满或者使用pg_switch_wal()后，会生成000000xxxx.ready文件，调用archive_command命令且成功执行后，将ready文件更名为.done文件。而数据库会在执行checkpoint后计算出最旧的需保留的WAL文件，比该值更早的WAL文件...
postgres 源码解析2 pg_basebackup
Serendipity_Shy
04-13 472
介绍     在postgres中pg_basebackup提供一个全量备份，可以将整个数据库实例的数据都拷贝出来，需要使用 replication协议连接到数据库实例上。该工具常用来搭建流复制环境，属于物理备份。逻辑备份工具时pg_dump pg_basebackup 参数介绍 [postgres@node196 data]$ pg_basebackup --help pg_basebackup takes a base backup of a running PostgreSQL server. Us
PostgreSQL逻辑复制解密
京东科技开发者
09-21 544
在数字化时代的今天，我们都认同数据会创造价值。为了最大化数据的价值，我们不停的建立着数据迁移的管道，从同构到异构，从关系型到非关系型，从云下到云上，从数仓到数据湖，试图在各种场景挖掘数据的价值。而在这纵横交错的数据网络中，逻辑复制扮演着及其重要的角色。 让我们将视角从复杂的网络拉回其中的一个端点，从PostgreSQL出发，对其逻辑复制的原理进行解密。
PostgreSQL patch: Allow a streaming replication standby to follow a timeline switch
weixin_33747129的博客
03-30 92
这个补丁不错, 省去了主从切换手工复制history文件的烦恼. Before this patch, streaming replication would refuse to start replicating if the timeline in the primary doesn't exactly match the standby. The...
postgresql 主从配置_PostgreSQL数据库主从部署
weixin_36012968的博客
01-15 3185
一、基础环境1、操作系统：CentOS 7.32、PostgreSQL：10.33、主节点：192.168.0.101 从节点：192.168.0.102二、部署主从1、安装postgreSQL主节点与从节点均安装postgreSQL，安装方法参考博客：CentOS系统下PostgreSQL数据库安装配置2、配置主从主节点(192.168.0.101)配置(1)创建归档目录mkdir -p /op...
Postgresql+Keepalived高可用方案
weixin_45428187的博客
10-23 2265
Postgresql+Keepalived高可用方案
诚之和:PostgreSQL流式复制入门经验分享！
weixin_45378258的博客
10-11 118
本篇文章中我们将深入探讨了在 PostgreSQL 中设置流复制 (SR) 的具体细节。流式复制是在PostgreSQL 托管中实现高可用性的基本构建块，它是通过运行主从配置生成的。 主从术语 主/主服务器 可以进行写入的服务器。 也称为读/写服务器。 从/备用服务器 数据与主服务器持续保持同步的服务器。 也称为备份服务器或副本。 暖备用服务器是在提升为主服务器之前无法连接的服务器。 相比之下，热备服务器可以接受连接并提供只读查询。在接下来的讨论中，我们将只关注热备服务器。 数据写入主服务器
postgres主备切换之文件触发方式
m15217321304的博客
03-27 5005
本文测试参考PostgresSQL实战一书。 本文档测试环境： 主库IP：192.168.40.130 主机名：postgres 端口：5442 备库IP: 192.168.40.131 主机名：postgreshot 端口：5442 PostgreSQL9.0版本流复制主备切换只能通过创建触发文件方式进行，这一小节将介绍这种主备切换方式，测试环境为一主一备异步流复制...
PostgreSQL primary-standby failback tools : pg_rewind(have bug)
weixin_34138521的博客
03-30 1084
将要加入PostgreSQL 9.5了 http://hlinnaka.iki.fi/2015/03/23/pg_rewind-in-postgresql-9-5/ https://github.com/vmware/pg_rewind 在数据库变得比较大时, 例如上TB, 如果部署了PostgreSQL primary-standby 流复制或者lo...
Git 撤销一个已经push到远端仓库的commit
qq_42429142的博客
09-25 556
如果想要保留历史记录，使用 git revert。如果你想完全删除某次提交，并修改历史，使用 git reset 然后强制推送 (–force)。选择方法时要小心，尤其是在共享分支上修改历史时。
git仓库服务器端损坏如何用本地code重新部署
江上清风山间明月的博客
09-22 563
Flutter是一个由Google开发的开源UI工具包，它可以让您在不同平台上创建高质量、美观的应用程序，而无需编写大量平台特定的代码。这样，你就将本地的最新代码重新部署到了新服务器上，并且保留了之前的所有修改记录。这会将新服务器设为默认的远程仓库，方便你以后继续推送和拉取代码。现在需要将本地的代码和所有的历史记录推送到新服务器的仓库中。此时，代码已经拉取到新服务器上，你可以进行正常的部署操作了。这个命令会推送你本地的所有分支到新服务器上的仓库。在新服务器上，你需要创建一个新的 Git 仓库。
Error: error:0308010C:digital envelope routines::unsupported
qq_45027843的博客
09-23 297
npm run dev项目启动报错 Error: error:0308010C:digital envelope routines::unsupported。
更新 Git 软件
MAMA6681的博客
09-22 458
更新 Git 软件本身是指将你当前安装的 Git 版本升级到最新版本。不同的操作系统有不同的更新方法。
You are not allowed to push code to this project
最新发布
Strawberry_ahh的博客
09-26 243
vscode无法提交前端代码
【ComfyUI】控制光照节点——ComfyUI-IC-Light-Native
进一寸有一寸的欢喜
09-23 943
IC-Light 是一个控制图像照明的项目。“IC-Light”这个名称代表“Impose Constant Light”（我们将在本页末尾简要描述这一点）。 目前，我们发布了两种类型的模型：文本条件重新光照模型和背景条件模型。两种类型都将前景图像作为输
CentOS 7快速指南：PostgreSQL 9.3二进制包安装教程
本文档是一份详细的Linux CentOS 7安装PostgreSQL 9.3的图文教程。Linux CentOS 7作为一款流行的开源操作系统，PostgreSQL是一款强大的对象关系型数据库管理系统，常用于服务器环境。本文针对的是二进制安装包的安装...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值