Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1h6IT3-00079M-DB for pgsql-hackers@arkaria.postgresql.org; Tue, 19 Mar 2019 17:24:01 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1h6IT2-0008AX-4r for pgsql-hackers@arkaria.postgresql.org; Tue, 19 Mar 2019 17:24:00 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1h6IT1-0008AQ-Tl for pgsql-hackers@lists.postgresql.org; Tue, 19 Mar 2019 17:23:59 +0000 Received: from n3.nabble.com ([162.255.23.22]) by magus.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1h6ISz-0002Zn-1d for pgsql-hackers@postgresql.org; Tue, 19 Mar 2019 17:23:59 +0000 Received: from n3.nabble.com (localhost [127.0.0.1]) by n3.nabble.com (Postfix) with ESMTP id 2A46612B0A051 for ; Tue, 19 Mar 2019 10:23:55 -0700 (MST) Date: Tue, 19 Mar 2019 10:23:55 -0700 (MST) From: Jim Finnerty To: pgsql-hackers@postgresql.org Message-ID: <1553016235129-0.post@n3.nabble.com> In-Reply-To: References: <21800.1552701008@sss.pgh.pa.us> <28191.1552753201@sss.pgh.pa.us> Subject: Re: Feature improvement: can we add queryId for pg_catalog.pg_stat_activity view? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk The queryId depends on oids, so it is not stable enough for some purposes. For example, to create a SQL identifier that survives across a server upgrade, or that can be shipped to another database, the queryId isn't usable. The apg_plan_mgmt extensions keeps both its own stable SQL identifier as well as the queryId, so it can be used to join to pg_stat_statements if desired. If we were to standardize on one SQL identifier, it should be stable enough to survive a major version upgrade or to be the same in different databases. ----- Jim Finnerty, AWS, Amazon Aurora PostgreSQL -- Sent from: http://www.postgresql-archive.org/PostgreSQL-hackers-f1928748.html