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 1uggZH-006IhJ-QG for pgadmin-support@arkaria.postgresql.org; Tue, 29 Jul 2025 09:24:20 +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 1uggZG-00GsP8-KW for pgadmin-support@arkaria.postgresql.org; Tue, 29 Jul 2025 09:24:18 +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 1uggZG-00GsOz-9I for pgadmin-support@lists.postgresql.org; Tue, 29 Jul 2025 09:24:18 +0000 Received: from four.baremetal.com ([67.223.102.125]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1uggZD-001M5V-1u for pgadmin-support@lists.postgresql.org; Tue, 29 Jul 2025 09:24:16 +0000 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=darrenduncan.net; h= message-id:date:mime-version:subject:to:references:from :in-reply-to:content-type:content-transfer-encoding; s= 2024062918; bh=FWS6kcIZbg8rtv00QuQ1pQhzTl0=; b=nH08RIyk+V1x7C7ov 6GnYUDZte1xzZXxwZBVCS9ZgK+Eu3cuZUKvIUKWZ/lxqe365Pp9P/zGBaRMN2/cM 2AHvUvfLNOvvcUEoLzrwwMTyhONCJjnAe/dpZjy3ap7602AaJheryRZWwmUBFjfq snNfjFEPaY92aSy3txPERdpX1I= Received: from [192.168.0.14] (107-190-19-247.cpe.teksavvy.com [107.190.19.247]) by four.baremetal.com (8.15.2/8.15.2) with ESMTP id 56T9ODpI058911 for ; Tue, 29 Jul 2025 02:24:13 -0700 Message-ID: <4a993f44-b02c-449e-ab98-51f100aace66@darrenduncan.net> Date: Tue, 29 Jul 2025 02:24:12 -0700 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Request to Remove Unused xmin Column from Function Properties Queries To: pgadmin-support@lists.postgresql.org References: Content-Language: en-US From: Darren Duncan In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk I had understood that Aurora mainly differed with its lower level internals implementation, but that it should look the same from a user perspective and thus be drop-in compatible with regular Postgres in practice, such that any database schemas or clients that work in regular should work with it unmodified. What are the main differences you see in Aurora that are surfaced to users such that they would have any kinds of impact on pgAdmin compatibility? Darren Duncan On 2025-07-29 1:37 a.m., Dave Page wrote: > Hi > > On Mon, 28 Jul 2025 at 15:00, Abhinav Patni wrote: > > Hi > I am seeing issues when using aurora postgres limitless. It doesn’t support > these columns, for function properties why do we need to query xmin value? > Is it supporting some other use case? > > Aurora isn't something we support, as it's different from PostgreSQL in many > ways. If xmin isn't used in this case (which seems likely), then I don't see any > reason not to remove it from the query, but there will likely be other ways in > which pgAdmin won't work properly with Aurora, that may not be so easy to fix. > > Please feel free to submit a pull request at https://github.com/pgadmin-org/ > pgadmin4 > > Thanks! > -- > Dave Page > pgAdmin: https://www.pgadmin.org > PostgreSQL: https://www.postgresql.org > pgEdge: https://www.pgedge.com >