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 1pKOAJ-00061P-Ss for pgsql-general@arkaria.postgresql.org; Tue, 24 Jan 2023 18:37:03 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pKO9K-0006cV-1Y for pgsql-general@arkaria.postgresql.org; Tue, 24 Jan 2023 18:36:02 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pKO9J-0006cL-Kd for pgsql-general@lists.postgresql.org; Tue, 24 Jan 2023 18:36:01 +0000 Received: from mail-ej1-x62e.google.com ([2a00:1450:4864:20::62e]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1pKO9H-0000VQ-GA for pgsql-general@postgresql.org; Tue, 24 Jan 2023 18:36:00 +0000 Received: by mail-ej1-x62e.google.com with SMTP id mg12so41470539ejc.5 for ; Tue, 24 Jan 2023 10:35:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:user-agent:message-id:date:subject:to:from:from:to:cc :subject:date:message-id:reply-to; bh=7b+dmh+T+oKW+mmm7ayimOAk/fYki1gWoyN71hMmZ2c=; b=pJROUqPnG5Y1yA3J0hqb4+R7rowcsbtBGslmZe698Qbl9k0mo256kE07y2/DBuAZ2p fFcHEuuqF7cF+kaN18zhs+RiPn2v2LUrCyszs4Q7D4w+3iOw1jzMQN6XfCbhuZ5Smi7s vXrqObvwyf9p9pftO5LuVJnJtD4BOnui307w4gOe3C/iobNcD3GcN7r+zglEckh7v9lo LxGeEdA4M30B/gx98rim5C2Oix19ysvqOqvo3guf9mlGs4UxmL1y5K9Q/zHTvxjHso2A nxggz8bW2kfZTUyh9JnlTj/vPSFxVBsOl/2KizLazuud4UMkhvjuTQNPibMGq5Gsmsjp JNVg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=mime-version:user-agent:message-id:date:subject:to:from :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=7b+dmh+T+oKW+mmm7ayimOAk/fYki1gWoyN71hMmZ2c=; b=Tw1xhBnURdsCBxAu49RDSjymjjOZkTygIOH8jKx9y4DCQpY0k8jK8FSlYn0kQb3TA+ 7cZvYoHxMysFyF9h3uRRRAlUrqJkCQRjnB31z39vk73jju5R5gUzmyPVF+3J7xRT0q+S cah3J3mzomDUeqsdtyXhHqKwyssA67HtMcmyhDJ8bREdycOcg/BQSXWJCIhiylUUAUu9 s/hl+oCaizBLso+Ud5lyYqDpDZCr0Co0WG4RLndtpafQxzCMF7ZbWQTe3uPZUc6vB5D+ OX5+rrTD6XKXhuIKUJH1EG4BPJSwtkiKUMlw+43m+B1lybPJWYTiion3mAgsRTtPn7Zf Ztbw== X-Gm-Message-State: AFqh2krEuWHDyZKhFKB48TdASEkK41kXtyPEk4mEZo48CRvtwzmpZmPH nZhnSiMZCbUkHUz/ChCz6zkvSo+KJZOgUQ== X-Google-Smtp-Source: AMrXdXv32n7XE5SRGk8O9DbRQXU7Td1Iwm9LPp6DXCNJb4ZD6hd04d9SG+Y0tMrHgEFu8dHDd2N3xg== X-Received: by 2002:a17:906:408:b0:86c:e07a:3cd5 with SMTP id d8-20020a170906040800b0086ce07a3cd5mr29951466eja.15.1674585357729; Tue, 24 Jan 2023 10:35:57 -0800 (PST) Received: from seb ([77.232.149.21]) by smtp.gmail.com with ESMTPSA id cf5-20020a170906b2c500b0084d37cc06fesm1253556ejb.94.2023.01.24.10.35.56 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 24 Jan 2023 10:35:56 -0800 (PST) From: Sergey Burladyan To: pgsql-general@postgresql.org Subject: Link WAL record to session Date: Tue, 24 Jan 2023 21:35:55 +0300 Message-ID: <87ilgv7pbo.fsf@gmail.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi, All! Is it possible to associate a WAL record with it session/process id? For example, if I have this record in WAL: rmgr: Standby len (rec/tot): 42/ 42, tx: 1142213518, lsn: 36174/FDC19050, prev 36174/FDC19020, desc: LOCK xid 1142213518 db 13091 rel 733108033 Can I find session that writes it? -- Sergey Burladyan