Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hNmep-00052k-Ss for pgsql-bugs@arkaria.postgresql.org; Mon, 06 May 2019 23:04:28 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hNmeo-0004LF-LN for pgsql-bugs@arkaria.postgresql.org; Mon, 06 May 2019 23:04:26 +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_SHA1:256) (Exim 4.89) (envelope-from ) id 1hNmeo-0004L8-Cy for pgsql-bugs@lists.postgresql.org; Mon, 06 May 2019 23:04:26 +0000 Received: from mail-qt1-x82a.google.com ([2607:f8b0:4864:20::82a]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hNmel-0002at-96 for pgsql-bugs@lists.postgresql.org; Mon, 06 May 2019 23:04:25 +0000 Received: by mail-qt1-x82a.google.com with SMTP id f24so6494347qtk.11 for ; Mon, 06 May 2019 16:04:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pushd.com; s=google; h=from:content-transfer-encoding:mime-version:subject:message-id:date :cc:to; bh=8U+EYYr8zPB/wmOUKyJ3O+XrSv2tkYjvW9ru+NAbyFE=; b=zppML8c9CyI7FIw+bJvQSw5kHoEBY3BFtjOoe9vjz0FH7ZF2R2ooGZS40JXKt370Ls bsjNQPD+jEF62F3PTC+epaMakKkVwcMRdAEyp10laMeWYwVq0yj1/p5hpvB1fYqj0DPH HFUXO8h+FHP04r37uCM0IRdKx5tljwPRQKQzc= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:message-id:date:cc:to; bh=8U+EYYr8zPB/wmOUKyJ3O+XrSv2tkYjvW9ru+NAbyFE=; b=eP00VKIvgciiUiGTKbtkK9UGWTTO06l1pcsqafWQh1zEhnlh7+iUdGBVsVqvPU8mv4 dn+WRNzuzGPIRDVIWw2A9VN01CAhAJyLPpXHHH6na2sNGXgXjihefbZ25kYWn9wMHkE8 TMrZqtarCBJ6npb9sfkYGaZwRogsvyc08bBi63hJLx4brwgqAO4dNyEMB4Y5L6XMZQaP ZBa00xKin0+8I/c9icyPSrzQbGhuC0oXOeqzk4Z457i6DEcPXZU2JXAh+wR1wGh+BUnB wQ2WJStbW4DAkKOU4ykUQnHm2VgpdDTUDpVbAa3p4ZVTlzgnw3OOYSdeU8VpP47CM851 9/bg== X-Gm-Message-State: APjAAAVkXyE40fLE4LwmGdNWmySqK0FVgl5IlFxQqG96I7MFNro5F+gy sXCzXxYjQFFyNRoAQ2VDZIXzEp8OOskw4g== X-Google-Smtp-Source: APXvYqw35kOcDmehJeHK4liAlJ0wdqELB/lBWizEa3IJyyGtzUHjZkk0QavCdsN3rFN63fb7xkuT9A== X-Received: by 2002:ac8:252b:: with SMTP id 40mr23583167qtm.384.1557183860448; Mon, 06 May 2019 16:04:20 -0700 (PDT) Received: from [10.0.42.121] (rrcs-24-103-40-170.nyc.biz.rr.com. [24.103.40.170]) by smtp.gmail.com with ESMTPSA id n36sm9132129qtk.9.2019.05.06.16.04.19 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 06 May 2019 16:04:19 -0700 (PDT) From: James Tomson Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.8\)) Subject: invalid memory alloc request size from pg_stat_activity? Message-Id: <1CFDCCD6-B268-48D8-85C8-400D2790B2C3@pushd.com> Date: Mon, 6 May 2019 19:04:18 -0400 Cc: Eric Jensen To: pgsql-bugs@lists.postgresql.org X-Mailer: Apple Mail (2.3445.104.8) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Hello, We're upgrading from postgresql 9.6 to 10.6 and everything is working = fine, but any query against pg_stat_activity results in ERROR: invalid = memory alloc request size 1652113408 e.g: ourdb=3D> SELECT pid, state, age(query_start, clock_timestamp()), = usename, query FROM pg_stat_activity WHERE query !=3D '' AND state = !=3D 'idle' ORDER BY age limit 100; ERROR: invalid memory alloc request size 1652113408 Maybe this has to do with us setting track_activity_query_size=3D102400? = Is there a known safe maximum for that, or could there be some other = problem? Thanks, James=