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 1ughPP-006RoM-TK for pgadmin-support@arkaria.postgresql.org; Tue, 29 Jul 2025 10:18:12 +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 1ughPP-00HQkg-0E for pgadmin-support@arkaria.postgresql.org; Tue, 29 Jul 2025 10:18:11 +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 1ughPO-00HQk2-P1 for pgadmin-support@lists.postgresql.org; Tue, 29 Jul 2025 10:18:11 +0000 Received: from four.baremetal.com ([67.223.102.125]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1ughPK-001SwW-2Q for pgadmin-support@lists.postgresql.org; Tue, 29 Jul 2025 10:18:10 +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=EjvedFBtNKhL8679MGxTVXHj2+s=; b=KTcYSqJQu/igpZDTz i1OGylUU7ZyNXK12gfAuDhkjU7VcCyIJkIorhZfYGOeqPIfZOPsaWH2v8Lh6gm82 DAeKxR9U/MMLUxggj+fni/Ql42Wr46X4pl9pfhUW7ja3P+Gd+1qA+763TVHPbELa ZAgVAdIowdRi3JVMZws5F6oH4Q= 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 56TAI48H069554 for ; Tue, 29 Jul 2025 03:18:04 -0700 Message-ID: Date: Tue, 29 Jul 2025 03:18:03 -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: <4a993f44-b02c-449e-ab98-51f100aace66@darrenduncan.net> Content-Language: en-US From: Darren Duncan 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 So it looks like there are at least 2 distinct versions of Postgres-compatible Amazon Aurora. The regular Aurora would have all the regular Postgres features I suppose. While the one you linked to is a specialized Distributed or DSQL variant and I see it is actually missing a huge amount of standard features, including foreign keys, sequences, triggers, exclusion constraints, and mixing DDL and DML in a common transaction. Darren Duncan On 2025-07-29 2:48 a.m., Dave Page wrote: > On Tue, 29 Jul 2025 at 10:24, Darren Duncan wrote: > > 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? > > > Things related to the underlying storage engine like system columns on tables, > for example xmin/xmax/ctid which might be different, but there are also a bunch > of unsupported features (https://docs.aws.amazon.com/aurora-dsql/latest/ > userguide/working-with-postgresql-compatibility-unsupported-features.html), none of which pgAdmin > knows are unsupported or in what way - e.g. are there system catalogues that are > missing, will DDL be accepted but do nothing or will it throw errors, will some > of the catalogues be missing individual columns that may not be needed because > certain features are unsupported? The list is likely longer than that, but you > get the gist. > > -- > Dave Page > pgAdmin: https://www.pgadmin.org > PostgreSQL: https://www.postgresql.org > pgEdge: https://www.pgedge.com >