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 1sTqRd-0033mR-87 for pgsql-hackers@arkaria.postgresql.org; Tue, 16 Jul 2024 22:14:49 +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 1sTqRb-004brK-KV for pgsql-hackers@arkaria.postgresql.org; Tue, 16 Jul 2024 22:14:47 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sTqRb-004brB-A7 for pgsql-hackers@lists.postgresql.org; Tue, 16 Jul 2024 22:14:47 +0000 Received: from mail-lf1-x12c.google.com ([2a00:1450:4864:20::12c]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sTqRT-002TsH-NO for pgsql-hackers@postgresql.org; Tue, 16 Jul 2024 22:14:46 +0000 Received: by mail-lf1-x12c.google.com with SMTP id 2adb3069b0e04-52ea952ce70so6444480e87.3 for ; Tue, 16 Jul 2024 15:14:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enterprisedb.com; s=google; t=1721168077; x=1721772877; darn=postgresql.org; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=HL87osYAGoK+EwRRrRxWb0bOD/uNoFEUFiPqbusAnjQ=; b=Ta9ApXu3lOOs4HA32AdJpAA0hWXxBXuySSJBGYC22dtZcQZsVVhQEfmliLMueNYv9x 7WB4KB1aVtJDB5G7u8QkYo3hMm2hgii6lKNnnDUcR3QMHRtY8IqCOxCAQ68W8394Vlem z2VBUcYKqC+SGhTYpsIyNvi4/kQxg5X4AAPK62+bPqhxrXGJ30lwCoZE6MUFw6PIC4j3 QrB8Kb6avihjlcitg+hQXZ0yMFGb2RzAMu+m3lzQePI2cEFvGdsuYu1q+cOP34cU2PwU l892/YV8LUb/J1lhlC5ntrIRGgYukLjHGcLrFZEyfGqSnaXtc2VccMheHNzbgPpQlQ1I J/fA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1721168077; x=1721772877; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=HL87osYAGoK+EwRRrRxWb0bOD/uNoFEUFiPqbusAnjQ=; b=LrPtIOQJmH3ww7P0C5iZRc9kbolMI2Cagf3b6gm0mOBvLbvOHXO4jVm0pWcnG7EV7S 03hE/ST1uMn3JTElFai6icbVz0YU24lfmfyvFzdWLEIzhqWFlUdBpczG3baFKDsWM+y0 ZJtpt+bEUmi9c247M2PdjxbsUYy2WGbXgcpDi60tRGO3b5aoXBhz6f92ekK08zvth0oq lpmDzE2+swO9zrwoSX9pycxNsDejCg9vYUbHPOb0b20fsGQjz7U/TKW3J/fSV8pLjK3e mCcBMoy3Wb+C15GBWBwSsDh+kbIxObCfPGXXVOa362nxPK4RFS3eeTZokUk1/4SGSucR kbqg== X-Gm-Message-State: AOJu0YwoH5x8WW4Q/5kI/l6rHI+RwWwHdTx4AYYybzikbxyJ3zUz6X6J yvkVEcxsPjLrisu302je6Xbw2AP7a7MjOkMol/DTsiZmVB7Epw6C55Pen3RsiQ== X-Google-Smtp-Source: AGHT+IEZ4l5VUE2gXMn7yLG+E3ENtg7mKHzpKH5jbA81AWDIOuVPnLXlyP+bAwteNNwvw9RotVujTA== X-Received: by 2002:a05:6512:23a3:b0:52e:7444:162e with SMTP id 2adb3069b0e04-52edf03868cmr2718664e87.55.1721168077234; Tue, 16 Jul 2024 15:14:37 -0700 (PDT) Received: from [10.137.0.18] (ip-86-49-229-30.bb.vodafone.cz. [86.49.229.30]) by smtp.gmail.com with ESMTPSA id a640c23a62f3a-a79bc820db8sm365152566b.213.2024.07.16.15.14.36 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 16 Jul 2024 15:14:36 -0700 (PDT) Message-ID: <5dc12198-80ff-4e70-b187-11ef33418411@enterprisedb.com> Date: Wed, 17 Jul 2024 00:14:36 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: RFC: pg_stat_logmsg To: Joe Conway , Gurjeet Singh , Masahiko Sawada Cc: PostgreSQL-development References: <89742024-d51a-c66b-90b9-67f837072cd2@joeconway.com> <3b1683bc-2630-a0d0-6083-8a45aa1b54bf@joeconway.com> Content-Language: en-US From: Tomas Vondra In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi, I noticed this patch hasn't moved since September 2023, so I wonder what's the main blocker / what is needed to move this? As for the feature, I've never done a fleet-wide analysis, so if this is one of the main use cases, I'm not really sure I can judge if this is a good tool for that. It seems like it might be a convenient way to do that, but does that require we add the module to contrib? As for the code, I wonder if the instability of line numbers could be a problem - these can change (a little bit) between minor releases, so after an upgrade we'll read the dump file with line numbers from the old release, and then start adding entries with new line numbers. Do we need to handle this in some way? This might be partially solved by eviction of entries from the old release - we apply decay, so after a while their usage will be 0. But what if there's no pressure for space, we'll not actually evict them. And it'll be confusing to have a mix of old/new line numbers. regards -- Tomas Vondra EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company