by default, database user passwords are stored as md5 hashes, so the administrator cannot determine the actual password assigned to the user. if md5 encryption is used for client authentication, the unencrypted password is never even temporarily present on the server because the client md5 encrypts it before being sent across the network.

the /contrib function library pgcrypto allows certain fields to be stored encrypted. this is useful if only some of the data is sensitive. the client supplies the decryption key and the data is decrypted on the server and then sent to the client.

the decrypted data and the decryption key are present on the server for a brief time while it is being decrypted and communicated between the client and server. this presents a brief moment where the data and keys can be intercepted by someone with complete access to the database server, such as the system administrator.

on linux, encryption can be layered on top of a file system mount using a "loopback device". this allows an entire file system partition be encrypted on disk, and decrypted by the operating system. on freebsd, the equivalent facility is called geom based disk encryption, or gbde.

this mechanism prevents unencrypted data from being read from the drives if the drives or the entire computer is stolen. this does not protect against attacks while the file system is mounted, because when mounted, the operating system provides an unencrypted view of the data. however, to mount the file system, you need some way for the encryption key to be passed to the operating system, and sometimes the key is stored somewhere on the host that mounts the disk.

the md5 authentication method double-encrypts the password on the client before sending it to the server. it first md5 encrypts it based on the user name, and then encrypts it based on a random salt sent by the server when the database connection was made. it is this double-encrypted value that is sent over the network to the server. double-encryption not only prevents the password from being discovered, it also prevents another connection from using the same encrypted password to connect to the database server at a later time.

ssl connections encrypt all data sent across the network: the password, the queries, and the data returned. the pg_hba.conf file allows administrators to specify which hosts can use non-encrypted connections (host) and which require ssl-encrypted connections (hostssl). also, clients can specify that they connect to servers only via ssl. stunnel or ssh can also be used to encrypt transmissions.

it is possible for both the client and server to provide ssl keys or certificates to each other. it takes some extra configuration on each side, but this provides stronger verification of identity than the mere use of passwords. it prevents a computer from pretending to be the server just long enough to read the password send by the client. it also helps prevent "man in the middle" attacks where a computer between the client and server pretends to be the server and reads and passes all data between the client and server.

if the system administrator cannot be trusted, it is necessary for the client to encrypt the data; this way, unencrypted data never appears on the database server. data is encrypted on the client before being sent to the server, and database results have to be decrypted on the client before being used.