aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2016-01-07 11:26:54 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2016-01-07 11:26:54 -0500
commit6b1a837f69d00d265bee4b57ba2d320f1463f131 (patch)
treed5a8790762356e32c31319712b7694676f2b5b03
parent5e0b5dcab685fe2a342385450a29a825cf40cddf (diff)
downloadpostgresql-6b1a837f69d00d265bee4b57ba2d320f1463f131.tar.gz
postgresql-6b1a837f69d00d265bee4b57ba2d320f1463f131.zip
Remove vestigial CHECK_FOR_INTERRUPTS call.
Commit e710b65c inserted code in md5_crypt_verify to disable and later re-enable interrupts, with a CHECK_FOR_INTERRUPTS call as part of the second step, to process any interrupts that had been held off. Commit 6647248e removed the interrupt disable/re-enable code, but left behind the CHECK_FOR_INTERRUPTS, even though this is now an entirely random, pointless place for one. md5_crypt_verify doesn't run long enough to need such a check, and if it did, this would still be the wrong place to put one.
-rw-r--r--src/backend/libpq/crypt.c2
1 files changed, 0 insertions, 2 deletions
diff --git a/src/backend/libpq/crypt.c b/src/backend/libpq/crypt.c
index f3c59e53036..d79f5a24968 100644
--- a/src/backend/libpq/crypt.c
+++ b/src/backend/libpq/crypt.c
@@ -81,8 +81,6 @@ md5_crypt_verify(const Port *port, const char *role, char *client_pass,
return STATUS_ERROR; /* empty password */
}
- CHECK_FOR_INTERRUPTS();
-
/*
* Compare with the encrypted or plain password depending on the
* authentication method being used for this connection. (We do not