Received: from malur.postgresql.org ([2a02:16a8:dc51::56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fRkuc-0001AM-9Q for pgadmin-hackers@arkaria.postgresql.org; Sat, 09 Jun 2018 20:56:38 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fRkua-00081o-CN for pgadmin-hackers@arkaria.postgresql.org; Sat, 09 Jun 2018 20:56:36 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fRkua-00081e-2g for pgadmin-hackers@lists.postgresql.org; Sat, 09 Jun 2018 20:56:36 +0000 Received: from mail-it0-x233.google.com ([2607:f8b0:4001:c0b::233]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1fRkuW-0002HD-Ou for pgadmin-hackers@postgresql.org; Sat, 09 Jun 2018 20:56:35 +0000 Received: by mail-it0-x233.google.com with SMTP id m194-v6so6275084itg.2 for ; Sat, 09 Jun 2018 13:56:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=codeweavers-net.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to :content-transfer-encoding; bh=jBFoZcuta6DBBcEXDPlS/Yk+bgw+JOt61ZTJKafFblo=; b=p2OdCULv3dB45N6gRp1LaVqRC1YwlL1X1QfH2laisjAbr8KtpGydAcUJpjJnl/V1KM qQbrLg0DwekJ6+T+Or/La14M358BH2hbkVIQnKb2nwTzHT5CqThiZThfSTZZnJnMkzOY ROQR+Q5X+jTX81HmAlaGBud4afhmKEDswahgHuhm+9nQe04HmNX6yzgot3OTYM9NEHwz gnlK5Jb+NM05MgTn9/cDkvl5KRKPU52RZQmCET8j+G4qvmAqKxVKpyLL1afY026RU8m0 +NayHjBlUbIIy731YUvw3VEKNRRIX4rYL0glsLOZWag2UFtXqUx7vgr1km26imoyZ8Gt 6EVQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to :content-transfer-encoding; bh=jBFoZcuta6DBBcEXDPlS/Yk+bgw+JOt61ZTJKafFblo=; b=db6o9sOlXe1QV7VajHmI0EWSSN9hMUVH+I5JHpsvdCImy46ropGOf2+FBf4mWkRRtM wvuNQUIA+5gnGjafBiWk9iOjK/xKjZTd8kZum5tFEVadKjHJakQNl5LQIzhJ+mAdtJ0s FnzCvxuhQxVDJM97oKKnnSpakIFHNvs6k8k1VMwzT3scxsgMt+S4p9ZtFUbxHijEoOkA vCKbgKsZtR62kCo4M9erXO8beoEX/iN2xPMcWjpdV90m5gofESM8TKdjaAJ/Svnw+2K3 aZSBIje8sueSavjC6O2mR4CSEA5H9hOPYxsahBQkBF2o2Cf+IcFhUi7RhEJE31HzIpC9 VBHw== X-Gm-Message-State: APt69E1MgWJnOP4dfY+Lx0lNV5TjgfCB0OIkWCGS4s1gPJT8tyIBe4hY uC0pnFE/ALgh6u7wAvdbQlnx0yNVEYSxHzagd/sQuFszqgPJCbRfTjz01JBHJpXeeS5KiX6iXyC NlVBwBzLHoygLMYYyeWeqjE6TUN92Ks4M33irlw== X-Google-Smtp-Source: ADUXVKKxGZf1TBt595dVV/WcVVfCm2LVKKPHLFHTvnEN7lCqE423xBxvI5Vg41OlzhY7SPvblFYHM+dp3g8Azq12Upo= X-Received: by 2002:a24:52cb:: with SMTP id d194-v6mr6654736itb.46.1528577789696; Sat, 09 Jun 2018 13:56:29 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a4f:9141:0:0:0:0:0 with HTTP; Sat, 9 Jun 2018 13:56:28 -0700 (PDT) From: Rob Emery Date: Sat, 9 Jun 2018 21:56:28 +0100 Message-ID: Subject: PGAgent 4.0 error feedback To: pgadmin-hackers@postgresql.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Hi Guys, I've been testing out PGAgent 4 (build today from master at commit 86ca5c5ed1ad572075ba27e05e4680ebdf5b9feb) to check the connection handling on error is still fixed with the boost reimplementation (which it is!) and noticed a few issues compared to PGAgent 3 around feedback to the user if the connection string is incorrect. I've tested with incorrect username and password, user not in the hba, db doesn't exist, postgresql not running on the host (or incorrect hostaddr) and 4 seems to always returns the error : ` ERROR: Couldn't find the function 'pgagent_schema_version' - please run pgagent_upgrade.sql. ` whereas 3.4.1 tends to output from the pgconnection itself like: ` Sat Jun 9 21:32:13 2018 : WARNING: Couldn't create the primary connection (attempt 1): FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL on FATAL: no pg_hba.conf entry for host "172.30.0.16", user "pgagent_login_role", database "pgagent_login_role", SSL off ` which at least points the user towards the actual error! Not sure if this is known already, but I thought I'd raise it prior to rele= ase. Thanks, Rob -- --=20 Codeweavers May Newsletter=20 =C2=A0=C2=A0l=C2=A0 Co= deweavers April=20 Finance Trends=20 April=E2=80=99s Dealer Highlights=20 =20 _ _ *Phone:*=C2=A00800 021 0888=C2=A0=C2=A0=C2=A0Email:=C2=A0contactus@codeweav= ers.net=20 Codeweavers Ltd=C2=A0| Barn 4 | Dunston=20 Business Village | Dunston | ST18 9AB Registered in England and Wales No.=20 04092394 | VAT registration no. 974 9705 63=C2=A0 =20 =C2=A0=C2=A0=20 =C2=A0=C2=A0=20 =C2=A0=C2= =A0=20