Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eEh8A-0002qu-VO for pgsql-admin@arkaria.postgresql.org; Tue, 14 Nov 2017 19:44:23 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1eEh89-0004TX-7o for pgsql-admin@arkaria.postgresql.org; Tue, 14 Nov 2017 19:44:21 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1eEh88-0004TJ-Da for pgsql-admin@postgresql.org; Tue, 14 Nov 2017 19:44:20 +0000 Received: from mail-lf0-x233.google.com ([2a00:1450:4010:c07::233]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1eEh80-0003Kg-H7 for pgsql-admin@postgresql.org; Tue, 14 Nov 2017 19:44:18 +0000 Received: by mail-lf0-x233.google.com with SMTP id w21so23591913lfc.6 for ; Tue, 14 Nov 2017 11:44:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nodalexchange.com; s=google; h=mime-version:from:date:message-id:subject:to; bh=nOmkgaHhGtO/ktUE/Et9drbqPckZCTVA0/Tni1EfsRQ=; b=NVIm73AbuomA1zHYuBaFLfjwME827gbWLctPNKlVbGfGYts14Nwy1eHqKtA5fuJHBV jsKmoovlV/kaci5OqbRWlWQNrSxPR54CRZeJxjsI42A0vzT28C4uPWYNw0AvtNOwbm3N pDUuv9U38X1myYT/unhT+YF8sQFYDKWLgxn+k= 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; bh=nOmkgaHhGtO/ktUE/Et9drbqPckZCTVA0/Tni1EfsRQ=; b=jzw0tF4D60JyiefGVoN4Pqvc9ZDWnuYgahb0GJdPbmb1/EWe19YUfEOQVtSGUT9qMf W/+CjJME8P4mfyJsTlwUt/EK+nfq6gIgAvJuDmCa4oS5N/UcTKkUrIaJO6YwlPO65aD6 ITRfhYBcEJfyfGPD7m5As+JWLnN/LxFG4tenzyxuLkMCe7C7fuMRTTpm9spjq0L825kU 3NzQ/kEzLTFBdy6Pm4nw/cvV8Nby5/nthw/4PyJPUOW09MsvogbMKG4yJFuW1eJqexuR wDKIh5z2bbVfa4Z9phMKOjzVLeN7TxOyjXgaeSCmfHfHWGpnBpgzL/eDiWtzEpg6sXdR cRSg== X-Gm-Message-State: AJaThX7h41j/WC7X8wQwsMXnp/mCoa1MZNCal4bGIDSg/zSplXqQNwis xX5SUH56Jeytpxaide2u3eplz6OcO/2LJ+cd32TmDslyJInNaA== X-Google-Smtp-Source: AGs4zMYm+L/G2clciO4jZtIKgKkSRguPMh4obUfmtCNVcOqpq/BbYjvVT8eV6fvIE3DI5R5cFZGdDSN1bnF763P0jGE= X-Received: by 10.25.43.144 with SMTP id r138mr5018913lfr.34.1510688648491; Tue, 14 Nov 2017 11:44:08 -0800 (PST) MIME-Version: 1.0 Received: by 10.25.42.6 with HTTP; Tue, 14 Nov 2017 11:44:08 -0800 (PST) From: Arjun Ranade Date: Tue, 14 Nov 2017 14:44:08 -0500 Message-ID: Subject: PG10 - Out of shared memory / invalid memory alloc request size To: pgsql-admin@postgresql.org Content-Type: multipart/alternative; boundary="001a114117d8428ac9055df69c7a" List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org --001a114117d8428ac9055df69c7a Content-Type: text/plain; charset="UTF-8" We recently upgraded a database that a number of developers use from Postgres 9.4 to 10. Our memory parameters are unchanged. We are seeing a lot of errors that look like this in the postgres log: < 2017-11-14 13:13:59 EST [144172] : [1-1] user=[unknown],db=qa16,remote=192.168.104.22(35238) > FATAL: no PostgreSQL user name specified in startup packet < 2017-11-14 13:52:22 EST [6273] : [1-1] user=deployment_app,db=qa5,remote=192.168.104.83(45384) > ERROR: out of shared memory < 2017-11-14 14:17:53 EST [6200] : [3-1] user=service_tracker_app,db=qa16,remote=192.168.104.22(46996) > ERROR: invalid memory alloc request size 34359738368 Anecdotally it seems that these errors are happening when powa_take_snapshot() (Postgres workload analyzer) is running as well but I can't confirm that. Does anyone know how to debug these types of errors? And once the db is in this state, how do we resolve sessions reporting "Error: invalid memory alloc request size" - killing the sessions and having them reconnect does not fix the issue. Thanks, Arjun --001a114117d8428ac9055df69c7a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
We recently upgraded a database t= hat a number of developers use from Postgres 9.4 to 10.=C2=A0 Our memory pa= rameters are unchanged.=C2=A0

We are seeing a lot of errors t= hat look like this in the postgres log:

< 2017-11-14 13:13:59 EST= [144172] : [1-1] user=3D[unknown],db=3Dqa16,remote=3D192.168.104.22(35238)= > FATAL:=C2=A0 no PostgreSQL user name specified in startup packet
&= lt; 2017-11-14 13:52:22 EST [6273] : [1-1] user=3Ddeployment_app,db=3Dqa5,r= emote=3D192.168.104.83(45384) > ERROR:=C2=A0 out of shared memory
<= ; 2017-11-14 14:17:53 EST [6200] : [3-1] user=3Dservice_tracker_app,db=3Dqa= 16,remote=3D192.168.104.22(46996) > ERROR:=C2=A0 invalid memory alloc re= quest size 34359738368

Anecdotally it seems that these errors = are happening when powa_take_snapshot() (Postgres workload analyzer) is run= ning as well but I can't confirm that.=C2=A0

Does anyone = know how to debug these types of errors?=C2=A0 And once the db is in this s= tate, how do we resolve sessions reporting "Error: invalid memory allo= c request size" - killing the sessions and having them reconnect does = not fix the issue.

Thanks,
Arjun
--001a114117d8428ac9055df69c7a--