Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pQ5pU-0006Qx-40 for pgsql-bugs@arkaria.postgresql.org; Thu, 09 Feb 2023 12:15:08 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pQ5pS-0002Ng-VW for pgsql-bugs@arkaria.postgresql.org; Thu, 09 Feb 2023 12:15:06 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pQ5pR-0002HF-Vv for pgsql-bugs@lists.postgresql.org; Thu, 09 Feb 2023 12:15:06 +0000 Received: from new4-smtp.messagingengine.com ([66.111.4.230]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pQ5pO-00039A-FD for pgsql-bugs@lists.postgresql.org; Thu, 09 Feb 2023 12:15:05 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailnew.nyi.internal (Postfix) with ESMTP id D209D5826BB; Thu, 9 Feb 2023 07:14:59 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Thu, 09 Feb 2023 07:14:59 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:date:feedback-id:feedback-id:from:from:in-reply-to :in-reply-to:message-id:mime-version:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; t=1675944899; x=1675952099; bh=Kb2PGwlGYNAC4 JswevsWw2y8VE3XThP7prOMGoqudFs=; b=gF/Bc4sIoTllgdI3oqnhsgEO7pKRX utMBXMeDoZx0hs4YrK6NCJtNKMdgLJheGXNHbAilUL8+t6J04Qe3txdLWoi1JVjf kIwCMRerO5UJlejRPIz+8NBdhSNiAhO5iwssx7s+nJEiNpYOqlCLT1tNSJej0fur Hy5RIoaVcgxnLyhTjRiOPqWHjY/J77URR+3UCVgvYz/S31QobLU2Ih3JsUxF3p65 K9RorS3U3jkydDGvBkCS5AQqcbFcTb3B7JPVZhycbVFM0CtosVU5yzuKLueQjWLA BEa8wcVhUu7IRZo2UXSATyxYeXZt6hDsDK32PvSkdCDXji6d6J7Bc7cCA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrudehfedgfeeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvuffkgggtugfgjgesthekre dttddtjeenucfhrhhomheptehlvhgrrhhoucfjvghrrhgvrhgruceorghlvhhhvghrrhgv segrlhhvhhdrnhhoqdhiphdrohhrgheqnecuggftrfgrthhtvghrnhepudejveejffejve duudetvdekieeuiedtvdeileefkeevjedufeeguedvjefhueelnecuffhomhgrihhnpegv nhhtvghrphhrihhsvggusgdrtghomhenucevlhhushhtvghrufhiiigvpedtnecurfgrrh grmhepmhgrihhlfhhrohhmpegrlhhvhhgvrhhrvgesrghlvhhhrdhnohdqihhprdhorhhg X-ME-Proxy: Feedback-ID: ia2694551:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 9 Feb 2023 07:14:58 -0500 (EST) Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id 478319C; Thu, 9 Feb 2023 13:14:56 +0100 (CET) Date: Thu, 9 Feb 2023 13:14:56 +0100 From: Alvaro Herrera To: roderick.zuniga@gmail.com, pgsql-bugs@lists.postgresql.org Subject: Re: BUG #17783: ERROR: could not open file "base/361098/2674030_vm": Operation not permitted Message-ID: <20230209121456.cyvigktiwxwomtey@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <17783-eeece73b58054152@postgresql.org> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 2023-Feb-08, PG Bug reporting form wrote: > The following bug has been logged on the website: > > Bug reference: 17783 > Logged by: Roderick Zuñiga > Email address: roderick.zuniga@gmail.com > PostgreSQL version: Unsupported/Unknown > Operating system: linux > Description: > > select * from public.pulsos_mensuales; > ERROR: could not open file "base/361098/2674030_vm": Operation not permitted Hmm, sounds like something changed the permissions for that file. Put them back so that they are like the permissions on all other files in that directory. -- Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/