Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1raJpw-009Bz0-Ir for buildfarm-members@arkaria.postgresql.org; Wed, 14 Feb 2024 18:18:24 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1raJpu-007qn2-Sc for buildfarm-members@arkaria.postgresql.org; Wed, 14 Feb 2024 18:18:22 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1raJpu-007qmR-Ma for buildfarm-members@lists.postgresql.org; Wed, 14 Feb 2024 18:18:22 +0000 Received: from mail-io1-xd36.google.com ([2607:f8b0:4864:20::d36]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1raJps-006kTf-8u for buildfarm-members@postgresql.org; Wed, 14 Feb 2024 18:18:21 +0000 Received: by mail-io1-xd36.google.com with SMTP id ca18e2360f4ac-7c475a6d81bso75819339f.1 for ; Wed, 14 Feb 2024 10:18:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1707934699; x=1708539499; darn=postgresql.org; h=content-disposition:mime-version:message-id:subject:to:from:date :from:to:cc:subject:date:message-id:reply-to; bh=6WWmd1IjxIc3m3Qtv9qfIwnDmLptYjopJtyykhA2TRo=; b=SttzKRab4fXz4xDxhgUQ2EjZ78w6W4xiGx2QEzx3EI0CE7VbOcrlPl5106NTzPHfY/ /r/mLqjPPtZNgQfqFHsoMNJWlLxJ4CEF+hFKWdDg4LzkF/5cI0r7pIrLYH1SGlc3FQpZ MCLS3k262zrUlD0T6dLSBh6/rXLauS4/j2yiuIAs0B6d+PNZPmd+h74iv4I+Tqg9IoAm ccqoR2hwcqQhnm64SS4Q7+FUrk+IY+2EunWKOc0NwHpkKbbG8SUlvWMN3XaHEW4zitZ3 JTzvt9ygPg1oH7syl+T/0sbx2UlMPRPGvhK+wh+X3z5VMXgAvu+XRqTRQZzmrGIenTKr CUxw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1707934699; x=1708539499; h=content-disposition:mime-version:message-id:subject:to:from:date :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=6WWmd1IjxIc3m3Qtv9qfIwnDmLptYjopJtyykhA2TRo=; b=MHAUigJN6VeyrpEMs8N7VPz72/nQJ/rMqc1Z8h5vQuSxZdEsE7fwfnK0aLk4RJ2Trw HMOzfHmZgf4LXPWbTTQ3kvjnvVvF5HeDVNHXqgCYeLjlY9S5tuPHOLmcJicgwVbxqT7D pjMViohKfNlooZbh85T3PvgCDusd4lcPfL3o4eLqZXImZN3zgM6mtdA/v59VyKr9J+Px mNByFfZzJRUkQYmD8c2hPNZ1Qpqy3ascYnOFGzqin5YFvprk2GxlvbmKQpYUbxdZYQz4 3+hdO3JxQq7aRlOszVZrleWjyR4e+Z9wnv/lBvK/ezKFVlZmiiCl1/qjyWb+eH180mLf GFRA== X-Gm-Message-State: AOJu0YxqEEs5cvRQhvX2uHeoXplNVbBjlSon5r8SOEog6fbBfEV8TlD1 oWNKlEPBUvk6OPWBOHIWzfReKXcj2wwmAGn4GVBqpSBb0RrxdyhlwQQBoIZc X-Google-Smtp-Source: AGHT+IHYDKUAU4yhLDBbkKaajLXNpBk5jQsUcfPI/vn9Sp44Hi00CHHbOcp4jIrFFZ7VeUV4Q69Z7w== X-Received: by 2002:a6b:ef0b:0:b0:7c4:69fd:860d with SMTP id k11-20020a6bef0b000000b007c469fd860dmr4030969ioh.1.1707934698994; Wed, 14 Feb 2024 10:18:18 -0800 (PST) Received: from nathanxps13 (162-195-168-172.lightspeed.stlsmo.sbcglobal.net. [162.195.168.172]) by smtp.gmail.com with ESMTPSA id k23-20020a02ccd7000000b004716652f89asm2561638jaq.130.2024.02.14.10.18.18 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 14 Feb 2024 10:18:18 -0800 (PST) Date: Wed, 14 Feb 2024 12:18:17 -0600 From: Nathan Bossart To: buildfarm-members@postgresql.org Subject: 413 Request Entity Too Large Message-ID: <20240214181817.GA370698@nathanxps13> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk My buildfarm machines 'akepa' and 'sevengill' periodically fail to report their status due to a "413 Request Entity Too Large" error. Are there any common tricks for trimming the logs to avoid this error (e.g., turning off log_statement)? Or should we consider raising the limit a bit? -- Nathan Bossart Amazon Web Services: https://aws.amazon.com