aboutsummaryrefslogtreecommitdiff
path: root/contrib/array/array_iterator.c
diff options
context:
space:
mode:
authorMarc G. Fournier <scrappy@hub.org>1996-08-14 04:56:55 +0000
committerMarc G. Fournier <scrappy@hub.org>1996-08-14 04:56:55 +0000
commit011ee13131f6fa2f6dbafd3827b70d051cb28f64 (patch)
treead5243989041a4da272c248714c11aa6ebde7b5e /contrib/array/array_iterator.c
parent6b9ecd83484e5e4c37fd59b29f83a10e9a5430d9 (diff)
downloadpostgresql-011ee13131f6fa2f6dbafd3827b70d051cb28f64.tar.gz
postgresql-011ee13131f6fa2f6dbafd3827b70d051cb28f64.zip
|
|We're all too familiar with psql's "no response from backend" message. |Users can't tell what this means, and psql continues prompting for |commands after it even though the backend is dead and no commands can |succeed. It eventually dies on a signal when the dead socket fills |up. I extended the message to offer a better explanation and made |psql exit when it finds the backend is dead. | |I also added a short message and newline when the user does a ctl-D so |it doesn't mess up the terminal display. | | Submitted by: Bryan Henderson <bryanh@giraffe.netgate.net>
Diffstat (limited to 'contrib/array/array_iterator.c')
0 files changed, 0 insertions, 0 deletions