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.96) (envelope-from ) id 1vKL8x-008Mh4-1G for pgsql-general@arkaria.postgresql.org; Sat, 15 Nov 2025 18:37:02 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vKL8u-00A029-2Z for pgsql-general@arkaria.postgresql.org; Sat, 15 Nov 2025 18:37:00 +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.96) (envelope-from ) id 1vKL8t-00A01z-2F for pgsql-general@lists.postgresql.org; Sat, 15 Nov 2025 18:37:00 +0000 Received: from fout-a8-smtp.messagingengine.com ([103.168.172.151]) by makus.postgresql.org with smtp (Exim 4.96) (envelope-from ) id 1vKL8r-007IVf-20 for pgsql-general@lists.postgresql.org; Sat, 15 Nov 2025 18:36:58 +0000 Received: from phl-compute-06.internal (phl-compute-06.internal [10.202.2.46]) by mailfout.phl.internal (Postfix) with ESMTP id 25DC3EC00EA; Sat, 15 Nov 2025 13:36:56 -0500 (EST) Received: from phl-mailfrontend-01 ([10.202.2.162]) by phl-compute-06.internal (MEProxy); Sat, 15 Nov 2025 13:36:56 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc:cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm2; t=1763231816; x=1763318216; bh=AXmFUB8nn2n2Gzr8vwG2qGVrYQ/byXLB3MJ0aIXjb7U=; b= kOR9jyaWN+p2eOIKVMKm8RGIsuBgJcAX9SLukZ5zA6pOgFNMNbGAgkWvK82qCIGs f2Bfe1SNJYbzSGFqNOnOPchVhYe/6JZZTKw3fjkfnUNqG9pZBB41DUeWbaE4WZ9n QrHD08vpOSBPf4z55Z3x8Vdtcg8wu7Lu8F/JODs6nkDMHRdLn8zOGg4ZyGN5T6JU nhYTtOcGxNYHkZ/wOGMtv+2BdofVWx0eK7FfxuIiBt9l3aqlcS7V0STnhQfjt8rE xm7thCHtpDjA/Hk5akpOTmbyMyntEjHHAkwyCBpVtl2lYXU8YThGCqXcP2vRP8NT C8imH90DvNCUglk5pKHymg== 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 :references:reply-to:subject:subject:to:to:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1763231816; x= 1763318216; bh=AXmFUB8nn2n2Gzr8vwG2qGVrYQ/byXLB3MJ0aIXjb7U=; b=S NShLHNkpAovwcQ5PoXjds40nEEah9k6+ITDNVTLvcbFSzd/2rcTzdkszr1AY54M0 9vI1i1Hmn5/wQBH+iC0ZS8NDFCuDQxInTDxluF1W8pWjbMlT9aphO4eIYiW9ikwE T3ghbQZMS6xFxWBADdTHIhgBcoEgW3IabI0zqBwBTa33fVBiXgnUwkz362NfEd07 znYvJZm7yXqx+N7YbcjiBVOvoFUhadjhyLm0tMeCZ3NnvJ7tnU6vaSVqsgUeOKT1 zisQXigEYLnwpZCyH971kYqyP24PsgEClDzqHznpsT4SP+ECO5Lrm0J4EZe7jViI Q5LWXHYuU5JlsN3ZyCjbA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeeffedrtdeggddvudefgeegucetufdoteggodetrf dotffvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfurfetoffkrfgpnffqhgenuceu rghilhhouhhtmecufedttdenucenucfjughrpefkffggfgfuvfevfhfhjggtgfesthejre dttddvjeenucfhrhhomheptegurhhirghnucfmlhgrvhgvrhcuoegrughrihgrnhdrkhhl rghvvghrsegrkhhlrghvvghrrdgtohhmqeenucggtffrrghtthgvrhhnpeejuedtgfeihe efueevhfekkeeljeeguddtvedvleegiedvhfduuddvtefhhfelffenucffohhmrghinhep ghhithhhuhgsrdgtohhmnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrg hilhhfrhhomheprggurhhirghnrdhklhgrvhgvrhesrghklhgrvhgvrhdrtghomhdpnhgs pghrtghpthhtohepfedpmhhouggvpehsmhhtphhouhhtpdhrtghpthhtohepphhmtgestg hithihlhhinhhkrdguihhnohgvgidrshhusgdrohhrghdprhgtphhtthhopehpghhsqhhl qdhgvghnvghrrghlsehlihhsthhsrdhpohhsthhgrhgvshhqlhdrohhrghdprhgtphhtth hopehlrghurhgvnhiirdgrlhgsvgestgihsggvrhhtvggtrdgrth X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sat, 15 Nov 2025 13:36:54 -0500 (EST) Message-ID: <512ab673-06c3-408c-9e42-19427f9fa9df@aklaver.com> Date: Sat, 15 Nov 2025 10:36:54 -0800 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: failure to drop table due to pg_temp_7 schema To: Peter 'PMc' Much Cc: pgsql-general@lists.postgresql.org, laurenz.albe@cybertec.at References: <8d0135f1-f69f-48bf-9956-9e64534cdf30@aklaver.com> Content-Language: en-US From: Adrian Klaver In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 11/15/25 10:10, Peter 'PMc' Much wrote: > On Sat, Nov 15, 2025 at 08:06:22AM -0800, Adrian Klaver wrote: > ! On 11/15/25 06:57, Peter 'PMc' Much wrote: > ! > > ! > Hi, > ! > ! > Que is this: https://github.com/que-rb/que > ! > ! Personally I would be more worried about an application > ! where the last commit was: > ! > ! Changelog: Add entry for version 2.4.1 > ! committed > ! on Oct 27, 2024. > > Really? I'd call that quite recently. > > And there is an explanation: Rails has dropped automated support > for Que. That doesn't matter to me, because I'm not using it in the > automated fashion. But it means the big user base is gone, and > therewith the influx of improvement desires. > > ! Makes you wonder what will happen if you upgrade to a newer version > ! of Postgres? > > I'll see when I'm there. Still have to wait for the new kerberos in > FreeBSD - there will be a lot more to mangle anyway. > > But speaking generally, I am quite bewildered that a simple tool > being stable for a year might already be considered worrisome. If the tool was self contained and did not rely on other software that might be alright. This tool does not, it has dependencies on Postgres and Rails and OS. They will be moving on. If you never change any of current versions of these then again you may be alright. Is that your intention? Then there is the issue of issues: https://github.com/que-rb/que/issues The last one was closed Jan 30, 2024, with six new ones added since then and 37 open ones from before. The question is it moving from stable to moribund? Or more to the point are you willing to do your own tech support for the tool? > Normally, a new technology brings a vast amount of innovation for > the first or second decade, and then it starts to stabilize. > We in the IT do the opposite, we ever increase the change rate, > and I am wondering where this is supposed to lead. > > cheers, > PMc -- Adrian Klaver adrian.klaver@aklaver.com