|
30 | 30 | * |
31 | 31 | * |
32 | 32 | * IDENTIFICATION |
33 | | - * $PostgreSQL: pgsql/src/backend/replication/walsender.c,v 1.21 2010/05/26 22:21:33 heikki Exp $ |
| 33 | + * $PostgreSQL: pgsql/src/backend/replication/walsender.c,v 1.22 2010/05/26 22:34:49 heikki Exp $ |
34 | 34 | * |
35 | 35 | *------------------------------------------------------------------------- |
36 | 36 | */ |
@@ -109,10 +109,10 @@ static void CheckClosedConnection(void); |
109 | 109 | * We don't have a good idea of what a good value would be; there's some |
110 | 110 | * overhead per message in both walsender and walreceiver, but on the other |
111 | 111 | * hand sending large batches makes walsender less responsive to signals |
112 | | - * because signals are checked only between messages. 128kBseems like |
113 | | - * a reasonable guess for now. |
| 112 | + * because signals are checked only between messages. 128kB(with |
| 113 | + *default 8k blocks) seems likea reasonable guess for now. |
114 | 114 | */ |
115 | | -#defineMAX_SEND_SIZE (128 *1024) |
| 115 | +#defineMAX_SEND_SIZE (XLOG_BLCKSZ *16) |
116 | 116 |
|
117 | 117 | /* Main entry point for walsender process */ |
118 | 118 | int |
|