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 1tnzdp-004Yzj-7h for pgsql-general@arkaria.postgresql.org; Fri, 28 Feb 2025 12:38:58 +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 1tnzdp-0059xo-AA for pgsql-general@arkaria.postgresql.org; Fri, 28 Feb 2025 12:38:55 +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 1tnzdo-0059xg-Vd for pgsql-general@lists.postgresql.org; Fri, 28 Feb 2025 12:38:55 +0000 Received: from mail-io1-xd2e.google.com ([2607:f8b0:4864:20::d2e]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1tnzdj-000Aga-25 for pgsql-general@postgresql.org; Fri, 28 Feb 2025 12:38:54 +0000 Received: by mail-io1-xd2e.google.com with SMTP id ca18e2360f4ac-855a095094fso57478639f.1 for ; Fri, 28 Feb 2025 04:38:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1740746331; x=1741351131; darn=postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=+pDlG8v+NaNloZSz6g9oyogFS22aq18fL2Lu8mmpf+8=; b=THJD2cRJpB6aKUaB6QLqN0RcJ9VrbfebILdpmVYleEKRUZIHfKPD4M6pHmv73pqVFz GFu9RYXmhncEbZQE8piGEqgnyphdualB2jGMbw1OSq6EhN9ujAT3uzCyS5+Q7GwypMQv HAulOWTcQbVk9h9p5C3RQXUK7rlTP+F7Y1fGw7VWiOVr/0F7zSgrqNRaLyafOsDbqeDU bRAcv6NLiEuJNb2S/O8YCQNdP3Toq9MLHt54rznou6M0DZJV3S9cwelZYCtulMyY1FYA MYEDflM+7qRMnZ42B+v8SzewL0vh0lHPTL3cSyzkn+aNvVkAogk43mZdnE+83VkcL81B ib+w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1740746331; x=1741351131; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=+pDlG8v+NaNloZSz6g9oyogFS22aq18fL2Lu8mmpf+8=; b=pXWMKBKiwr1YsW13W4l4MWry9JKaw4g+OnKoENzgdG74B+drYAaU+lrFV+aTU3fUjP tRXOZ0kuLG2pvXaVGgGthg+Y1OCaPniIU7mbQeDU0u6TBwg07YdPnBqaycUglOv9xu8x 0aqd5VOzR/e0GPhrUItGo9+7bgb3PXO4wA6hk9812JbTL36LSLbuExPjLQQ4fv3OJ7iS GvWYXo17x8UXAE0ubwMSSC7pftafQ7iRvk2EDYUQRIZlwdcdcRXhNeXcoYIjk5uh1IUD gIMHwwzoeElW3Mnkt+N8YXOv34+czfe7jQmq0gBP2SKYPzTFu9z773QI94xTkmC+wdKY x6BA== X-Gm-Message-State: AOJu0YzwkGfcfuXTO5jcI9Ybh6G3exSZBHTQROkI1l2oZjyAtZaYiiW0 iU7r3NHMfFEDIKK/t49LKmaXQFWlvWu+LichvQ7drjc5tJsFeGXvKsnsN9Avj5WJQLHQlRokmx1 f433UQW8zUoFqh6tJ+eG1GZW9iko= X-Gm-Gg: ASbGncuwz5Cei2kgGZH6zbVap1c9oddR+fKSDCuCEMX8QLspEHAT9lnCXisgaLLe9fz oAT8DDX5NWiL/nnWgRCNi13yM+5c2zik96I5jlk0ZoSE4+N1ZISyN+hIdnzeevyexTxWoPvBGBy NkrcgJTNsyQdbBt8dmw6qJ6sXv+d6vnA2OSKsXjxR/2A== X-Google-Smtp-Source: AGHT+IGHHAMTkopmXcu1HVoRYEDBZlbOgsNz11p3vIZp5JvRR1zW4+C1jbQNnRuDGqSRrKg5kWSHVIBGdKpa4T+dbT4= X-Received: by 2002:a05:6e02:12ea:b0:3d3:dfb6:2203 with SMTP id e9e14a558f8ab-3d3e6f4a094mr26575245ab.19.1740746331121; Fri, 28 Feb 2025 04:38:51 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Greg Sabino Mullane Date: Fri, 28 Feb 2025 07:38:14 -0500 X-Gm-Features: AQ5f1JoN4Y1T_4tnVyub7qERhmiGR8RNrPH46Ke-8OVN8Rk36jR7Qd22Zhi9sEM Message-ID: Subject: Re: Long Running query and trace potential issues To: KK CHN Cc: pgsql-general Content-Type: multipart/alternative; boundary="000000000000b5f7d1062f331644" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000b5f7d1062f331644 Content-Type: text/plain; charset="UTF-8" That's harmless, it is the walsender process, and it is meant to be long-running. You can modify your query and add this: AND backend_type = 'client backend' to filter out any background processes. Cheers, Greg -- Crunchy Data - https://www.crunchydata.com Enterprise Postgres Software Products & Tech Support --000000000000b5f7d1062f331644 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
That's harmless, it is the walsender = process, and it is meant to be long-running. You can modify your query and = add this:

AND backend_type =3D 'client backend'<= /div>

to filter out any background processes.
=

<= div dir=3D"ltr">
Cheers,
Greg

--
Enterprise Postgres Software= Products & Tech Support

--000000000000b5f7d1062f331644--