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 1lkdQ4-0000ld-HN for pgsql-sql@arkaria.postgresql.org; Sun, 23 May 2021 02:00:44 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lkdQ1-0000Jl-Ew for pgsql-sql@arkaria.postgresql.org; Sun, 23 May 2021 02:00:41 +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 1lkdQ1-0000Jc-2w for pgsql-sql@lists.postgresql.org; Sun, 23 May 2021 02:00:41 +0000 Received: from mail-pf1-x434.google.com ([2607:f8b0:4864:20::434]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1lkdPt-0004tg-Ng for pgsql-sql@lists.postgresql.org; Sun, 23 May 2021 02:00:40 +0000 Received: by mail-pf1-x434.google.com with SMTP id d16so17905048pfn.12 for ; Sat, 22 May 2021 19:00:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gisticinc-com.20150623.gappssmtp.com; s=20150623; h=subject:references:to:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=CVWADmdMrs5bghwZXTO0fsFS9JoqrnQPpFO5zvEYGbo=; b=Ikr5uwW5SGJzKg/VyCC3XN2Ojbn2VvW6sWqatKeqkSypVgiRay6dAPlhuscF59syQQ Qiy2bqooxBuF08ZENd/XNdg0lGbNv5ceRq/Ms8GCSG4pS3HGT7bTS2p9te0h+T8bh8DQ b2AjRP4P0SN9plHnD4ucOEZ72lY0IVr0wMycidvSA8jkVdgFSdw1oH1OHzQ+T5YOq7zX Oa0dkMaJn9UycJMX3uzdNKUSBK7ZLCBlcQOxx0dhqh3NNN//6iOE/UWhJmJrAqE7cZUN iUhnNLvYex2kxdMMxWXCVJq6AdHBL/oNslnB8zsLFvcRg40sugC5WRAAkhcTUKC6h+Uq C1kQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:references:to:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=CVWADmdMrs5bghwZXTO0fsFS9JoqrnQPpFO5zvEYGbo=; b=mugUi282RQQtyOCft8jYVLVgROJHzK/Mzxbr9HrdNYdjUcYcGXEIJ7np4+tmTyrMf2 PO1nfav7JnzobFE55eQNjNYsZ6LnHgjrZuOJa6RJPZaisQOFQZE84RN/dcDflFrutapO 1r5RHG/WW+IRvQJU+3jsbUJlYrSdUQlTVr4zymhglCxpay2cqd5/1lCPG4Z2HMWjBo0k 4Q3Kkn/oZi04k2NJ5NP+MGKhrKTdUwRUv7M1Jim2Lb2tc2nGR0IEuw7lwnYD0ZLSOBKj ymS5JNqJRoZh7nF2iwZ7krpMWGX2rbSFJWofd7Wtx1qSIHyOOhDMnLdGwOY/t618sKOE giCw== X-Gm-Message-State: AOAM532WcQajNflmXhIJIlWaPTtT1iLm/TEL5CCUTsofDeTiQqSuZim3 eX4qc36CZ7d26KDQ7bnEKmER7vwB4zcergTs X-Google-Smtp-Source: ABdhPJzMyHo0CLisADkWEhHOsoYOWmQ/YMvWSWx9hmoYq6s9yKZP08Z1EYq9IoDdOrgcfQCbcXON2Q== X-Received: by 2002:a62:d108:0:b029:25d:497e:2dfd with SMTP id z8-20020a62d1080000b029025d497e2dfdmr17922347pfg.29.1621735230367; Sat, 22 May 2021 19:00:30 -0700 (PDT) Received: from snowflake.tempe.gistic.com (wsip-72-215-195-71.ph.ph.cox.net. [72.215.195.71]) by smtp.gmail.com with ESMTPSA id ie5sm11658060pjb.14.2021.05.22.19.00.29 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 22 May 2021 19:00:30 -0700 (PDT) Subject: Getting transaction details from the WAL? References: <1510da2a-da65-3af7-4a83-88f5856de1fb@gisticinc.com> To: pgsql-sql@lists.postgresql.org From: Bo Guo X-Forwarded-Message-Id: <1510da2a-da65-3af7-4a83-88f5856de1fb@gisticinc.com> Message-ID: <52014f4e-b1d5-06fd-660e-b58f4f1188de@gisticinc.com> Date: Sat, 22 May 2021 19:00:27 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.8.1 MIME-Version: 1.0 In-Reply-To: <1510da2a-da65-3af7-4a83-88f5856de1fb@gisticinc.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hello, PostgreSQL community! I am wondering if it is possible to get content changes to a particular table from a point-in-time by exploring the WAL or any other artifacts relating to transaction management. Any help or comment is appreciated! Cheers, Bo