Skip to content

Fix auth_query example to avoid 'bouncer config error' when no user is found #15

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 5 additions & 6 deletions config.md
Original file line number Diff line number Diff line change
Expand Up @@ -1626,14 +1626,13 @@ Database examples:

Example of a secure function for `auth_query`:

CREATE OR REPLACE FUNCTION pgbouncer.user_lookup(in i_username text, out uname text, out phash text)
RETURNS record AS $$
CREATE OR REPLACE FUNCTION pgbouncer.user_lookup(i_username text)
RETURNS TABLE (uname text, phash text) AS $$
BEGIN
SELECT rolname, CASE WHEN rolvaliduntil < now() THEN NULL ELSE rolpassword END
RETURN QUERY
SELECT rolname::text, CASE WHEN rolvaliduntil < now() THEN NULL ELSE rolpassword END
FROM pg_authid
WHERE rolname=i_username AND rolcanlogin
INTO uname, phash;
RETURN;
WHERE rolname=i_username AND rolcanlogin;
END;
$$ LANGUAGE plpgsql
SECURITY DEFINER
Expand Down