From: Neil Conway Date: Sat, 5 Aug 2006 00:29:14 +0000 (+0000) Subject: Fix references to the Options section in the pgcrypto documentation. X-Git-Url: http://git.postgresql.org/gitweb/static/gitweb.js?a=commitdiff_plain;h=1a1339d1148b47eaa629e6bfec19a883bf3c299f;p=users%2Fbernd%2Fpostgres.git Fix references to the Options section in the pgcrypto documentation. Patch from Michael Fuhr. --- diff --git a/contrib/pgcrypto/README.pgcrypto b/contrib/pgcrypto/README.pgcrypto index 84c76298b4..15e5232e3f 100644 --- a/contrib/pgcrypto/README.pgcrypto +++ b/contrib/pgcrypto/README.pgcrypto @@ -327,7 +327,7 @@ Now common part, the session-key encrypted data packet: Return a symmetric-key encrypted PGP message. -Options are described in section 5.7. +Options are described in section 5.8. 5.3. pgp_sym_decrypt(msg, psw) @@ -342,7 +342,7 @@ Decrypting bytea data with `pgp_sym_decrypt` is disallowed. This is to avoid outputting invalid character data. Decrypting originally textual data with `pgp_sym_decrypt_bytea` is fine. -Options are described in section 5.7. +Options are described in section 5.8. 5.4. pgp_pub_encrypt(data, pub_key) @@ -354,7 +354,7 @@ Options are described in section 5.7. Encrypt data with a public key. Giving this function a secret key will produce a error. -Options are described in section 5.7. +Options are described in section 5.8. 5.5. pgp_pub_decrypt(msg, sec_key [, psw]) @@ -374,7 +374,7 @@ Decrypting bytea data with `pgp_pub_decrypt` is disallowed. This is to avoid outputting invalid character data. Decrypting originally textual data with `pgp_pub_decrypt_bytea` is fine. -Options are described in section 5.7. +Options are described in section 5.8. 5.6. pgp_key_id(key / msg)