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 1rk50n-00AA3V-C5 for pgsql-general@arkaria.postgresql.org; Tue, 12 Mar 2024 16:29:58 +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 1rk50l-00Ftue-D5 for pgsql-general@arkaria.postgresql.org; Tue, 12 Mar 2024 16:29:55 +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 1rk50k-00FtuW-1J for pgsql-general@lists.postgresql.org; Tue, 12 Mar 2024 16:29:55 +0000 Received: from wfhigh4-smtp.messagingengine.com ([64.147.123.155]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rk50g-0048u7-FX for pgsql-general@lists.postgresql.org; Tue, 12 Mar 2024 16:29:53 +0000 Received: from compute6.internal (compute6.nyi.internal [10.202.2.47]) by mailfhigh.west.internal (Postfix) with ESMTP id 8586B1800098; Tue, 12 Mar 2024 12:29:46 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute6.internal (MEProxy); Tue, 12 Mar 2024 12:29:46 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :reply-to:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t=1710260986; x= 1710347386; bh=SEYHCFVIscrtvIqw9ug5RfjF5//F/4wgQnkTGKnH9PU=; b=P H8KwLkxDFOFPgLRnWEqixhT2OyuLGPyrzmYbPV1Yffr/LwnOdyJmLpB1NLo0gblG 9fUPrBlCT0dKUtlRGf3QkJ+8JTOF+SPMZbuLmEd6InBfMPw1drIIF08Ljoos0tqz DhBJw2eIGcTCccHm20MYWq/SHuxUtEpW8q2ttW+zjr0jMWu19UzhWUvR/JCjm1HL C1dm1BTrBGhrz8394kbNHqHuNHHejc1CTlVeyDCrXHj9eE4ZNOIz8sKlLJN/Jf6v 5CTYFi9kZeuY0Q7vY2ROxwY2IgKoDPwtdhc0d8qIeRjg4ZWqchfB1KVyCMH0ZJnj 5TxWpTEYQzMDAfLZecLNA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrjeefgdekkecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpeffhffvvefukfggtggugfgjsehtkeertddttdejnecuhfhrohhmpeetlhhvrghr ohcujfgvrhhrvghrrgcuoegrlhhvhhgvrhhrvgesrghlvhhhrdhnohdqihhprdhorhhgqe enucggtffrrghtthgvrhhnpedvkedtffduffdtffffheffhfejjefhgfeiueeukeejkeff gfdufffhudffffeuveenucffohhmrghinhepvghnthgvrhhprhhishgvuggsrdgtohhmne cuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomheprghlvhhh vghrrhgvsegrlhhvhhdrnhhoqdhiphdrohhrgh X-ME-Proxy: Feedback-ID: ia2694551:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 12 Mar 2024 12:29:45 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=alvh.no-ip.org; s=schmee; t=1710260981; bh=q9uI19Cs7Cc4Z/09C3bbmkWOn76AIOkuaUpmC7ysReI=; h=Date:From:To:Cc:Subject:In-Reply-To:From; b=nxBk+0q/9guEI7V/2mOw0sHuvMs3NWobokNsNak4zmdzGsLo8+2ZHn1b+RssEuT3Z tDyLPQ6+IedkswxHpm6KXTOSSKuZc8poLJU66TzutwZsOsxHaNpv7n1n3fYYsHXJRS Oofuaq/eUVKIbZUrrxwswyrzdSN/vmscMCwGlpNfw51yudeGYN6rS1RlAczOLqOH5Y YPG1vROLWGEGOl1uWRsWYgCT5dAqDkWYheOX/NffZOYRensLyPHHwxLA6LtuAY3HVk aNq7DPSrNn/GZnAO/cP6d8hPp+rR5WtcwC6fO/PJKHJTJK0eWrEujcn7YI9KA6O/Am HdfdupXDPHq7w== Received: by schmee.alvh.no-ip.org (Postfix, from userid 1000) id EA388CD5; Tue, 12 Mar 2024 17:29:41 +0100 (CET) Date: Tue, 12 Mar 2024 17:29:41 +0100 From: Alvaro Herrera To: Dominique Devienne Cc: pgsql-general@lists.postgresql.org Subject: Re: Is it possible to keep track of SELECTs? Message-ID: <202403121629.ukxkmq4vldhm@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 2024-Mar-12, Dominique Devienne wrote: > So is it possible to track the last time a SELECT was performed on some > TABLE? Perhaps you could use the pgAudit module for this purpose. -- Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/