diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2012-06-29 00:51:40 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2012-06-29 00:51:40 -0400 |
| commit | f374098e8c5f58b95e03b923c8a808cdeeea93e7 (patch) | |
| tree | b6d9b263173f3009c5aaea5c9278c74599246c61 /src/backend/parser/parse_utilcmd.c | |
| parent | c8967e38a65e4afac7027d570136ca6dac5cacc1 (diff) | |
| download | postgresql-f374098e8c5f58b95e03b923c8a808cdeeea93e7.tar.gz postgresql-f374098e8c5f58b95e03b923c8a808cdeeea93e7.zip | |
Fix NOTIFY to cope with I/O problems, such as out-of-disk-space.
The LISTEN/NOTIFY subsystem got confused if SimpleLruZeroPage failed,
which would typically happen as a result of a write() failure while
attempting to dump a dirty pg_notify page out of memory. Subsequently,
all attempts to send more NOTIFY messages would fail with messages like
"Could not read from file "pg_notify/nnnn" at offset nnnnn: Success".
Only restarting the server would clear this condition. Per reports from
Kevin Grittner and Christoph Berg.
Back-patch to 9.0, where the problem was introduced during the
LISTEN/NOTIFY rewrite.
Diffstat (limited to 'src/backend/parser/parse_utilcmd.c')
0 files changed, 0 insertions, 0 deletions