Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nf54t-0005YR-DQ for pgsql-admin@arkaria.postgresql.org; Thu, 14 Apr 2022 19:24:27 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nf54s-0002CB-9n for pgsql-admin@arkaria.postgresql.org; Thu, 14 Apr 2022 19:24:26 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nf54r-0002C1-TP for pgsql-admin@lists.postgresql.org; Thu, 14 Apr 2022 19:24:25 +0000 Received: from mail-ed1-x533.google.com ([2a00:1450:4864:20::533]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1nf54l-0005nt-G6 for pgsql-admin@lists.postgresql.org; Thu, 14 Apr 2022 19:24:24 +0000 Received: by mail-ed1-x533.google.com with SMTP id g20so7589291edw.6 for ; Thu, 14 Apr 2022 12:24:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=UmSATnyLtT4j8fwSnJFC2uleMOO4/p/+CVoQgfBt9wU=; b=NNl+un9VP5+5yjmmaHznP3SA6EgousQ+DSpOYldIA9uSWH97kFGrhhwkgatLcjayhJ O4O4wBM0lLsS331yowgvbST75JDEG6/x27bo6Y8g9Jk9KCtC3oKF4MMshzE4uFVtDEi0 PexmBM86luXoTUhaXXkI5De/gECQbPPCvFNPU+y5CQwSbdChhCe2FPmf6UlGJcJWZpY0 ZIWjOjOEeJ8fM/vYZZhdTEq0MoqZ1pvIOWz19eWznIoPKbz7jQOgPExbqtDta+QgUSpv B+FiapGP2HOxQZK3J5j8DLoaW748tonez60fy4DOlS0LZhSizAhxnoScY5EMVmk0C53H 6tuA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=UmSATnyLtT4j8fwSnJFC2uleMOO4/p/+CVoQgfBt9wU=; b=QoPxJQlr6OcD/rc/PIeyFgTNeYcBwSh4OtZb+AqAtqWTX0DH0kudk+5U5+oUYxqzhL YbTdJ9EcxHU82tf/UBslOQV28AwEKNkDuT59cuDS/uPlVVsS+Zyah9UYS7IAw88pGOBS EgT0/LFxjkpT95fXEP3OcKb3HOKX7MrmX9u/PWaTX2CTls/eCf2CO/taYhWOKn+cYguR iHWtjKSjVrWMPwjiX7AmzVwTNZxOvmYKtfS87QtdG3ppCaKo1UipTCDWXkdrm9K9yJgz xlj+syvIww8ZlxemgYJZ8TzvvfDmlJ6EmsF8UYKCjUTolmgud1ECnJsrwMoW7LFlhNZU M0Uw== X-Gm-Message-State: AOAM533yE4vWy7sFJQXLYC8sxTWWXm8zcWr0QKAH0o4K/exiuJVG711c xP5Y7Sw0CV5je+QRZX2Ar9l3fluxmWTjt+gt5Kzmq191 X-Google-Smtp-Source: ABdhPJzhSH7HPD0MiU/PIhLljLB5tDrKM4orLzlGAARUdAkTIvwwU1vycx5mv2tCE0uK/YU9cU1Q69dV/2KIdRSYmMY= X-Received: by 2002:a50:954b:0:b0:41a:c9cb:8778 with SMTP id v11-20020a50954b000000b0041ac9cb8778mr4649513eda.165.1649964257961; Thu, 14 Apr 2022 12:24:17 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a05:640c:28c5:b0:153:e47f:8e68 with HTTP; Thu, 14 Apr 2022 12:24:17 -0700 (PDT) In-Reply-To: References: From: "David G. Johnston" Date: Thu, 14 Apr 2022 12:24:17 -0700 Message-ID: Subject: Re: query to show locked / disabled users? To: Sbob Cc: Pgsql-admin Content-Type: multipart/alternative; boundary="0000000000007ce95305dca23d25" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000007ce95305dca23d25 Content-Type: text/plain; charset="UTF-8" On Thursday, April 14, 2022, Sbob wrote: > I have a client that says there were break in attempts and many db users > are now disabled / locked because of too many wrong pw attempts. Is there > a select that will show these users? > > You can look at pg_roles. David J. --0000000000007ce95305dca23d25 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thursday, April 14, 2022, Sbob <sbob@quadratum-braccas.com> wrote:
I have a client that says there were break in attempts and many d= b users are now disabled / locked because of too many wrong pw attempts. Is= there=C2=A0 a select that will show these users?


=C2=A0You can look at pg_roles.
=
David J.

--0000000000007ce95305dca23d25--