-
- Downloads
Automatically terminate replication connections that are idle for more
than replication_timeout (a new GUC) milliseconds. The TCP timeout is often too long, you want the master to notice a dead connection much sooner. People complained about that in 9.0 too, but with synchronous replication it's even more important to notice dead connections promptly. Fujii Masao and Heikki Linnakangas
Showing
- doc/src/sgml/config.sgml 28 additions, 0 deletionsdoc/src/sgml/config.sgml
- src/backend/libpq/pqcomm.c 171 additions, 69 deletionssrc/backend/libpq/pqcomm.c
- src/backend/port/unix_latch.c 19 additions, 7 deletionssrc/backend/port/unix_latch.c
- src/backend/port/win32/socket.c 12 additions, 1 deletionsrc/backend/port/win32/socket.c
- src/backend/port/win32_latch.c 24 additions, 6 deletionssrc/backend/port/win32_latch.c
- src/backend/replication/walsender.c 98 additions, 45 deletionssrc/backend/replication/walsender.c
- src/backend/utils/misc/guc.c 10 additions, 0 deletionssrc/backend/utils/misc/guc.c
- src/backend/utils/misc/postgresql.conf.sample 1 addition, 0 deletionssrc/backend/utils/misc/postgresql.conf.sample
- src/include/libpq/libpq.h 3 additions, 0 deletionssrc/include/libpq/libpq.h
- src/include/replication/walsender.h 1 addition, 0 deletionssrc/include/replication/walsender.h
- src/include/storage/latch.h 1 addition, 1 deletionsrc/include/storage/latch.h
Loading
Please register or sign in to comment