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.96) (envelope-from ) id 1weAcH-004bz4-17 for pgsql-hackers@arkaria.postgresql.org; Mon, 29 Jun 2026 11:57:33 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1weAcG-0031Ps-0e for pgsql-hackers@arkaria.postgresql.org; Mon, 29 Jun 2026 11:57:32 +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.96) (envelope-from ) id 1weAcF-0031Pk-2X for pgsql-hackers@lists.postgresql.org; Mon, 29 Jun 2026 11:57:31 +0000 Received: from mail-wm1-x332.google.com ([2a00:1450:4864:20::332]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.98.2) (envelope-from ) id 1weAcD-00000000mXM-0GAG for pgsql-hackers@lists.postgresql.org; Mon, 29 Jun 2026 11:57:31 +0000 Received: by mail-wm1-x332.google.com with SMTP id 5b1f17b1804b1-49319ebb3a9so12439435e9.3 for ; Mon, 29 Jun 2026 04:57:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec.at; s=google; t=1782734247; x=1783339047; darn=lists.postgresql.org; h=message-id:date:mime-version:subject:cc:to:from:from:to:cc:subject :date:message-id:reply-to; bh=2IkBnUkKy2XxZrEIuYpIqfqQ1xaokQJlPanTzI+zHG0=; b=eIi96cghLvZpZOcB1uM6yu2gzxvsGZJLkWlCVjlmQjs53HsL4fMxv/DNmzhLu1p65B Ru0WW4aOCkAq1z1ZnY6XPIps5D1fm2Ty3BILS/BvzVjgaJW8V7ti6UaplrNAngu7AjyE j5ubi4g4TYFtRbkEuhNr68dCg3J7qZoRdZlqkMO4dcIDwhqOsFsEnrv2nE9cCXECueJ5 8RwLtDvqVT5/1Cl7AJn43SYSTsa3AtgiUcH2DoChXe6ASqKWnG7dt9Joek6zq6MLCVy3 5bj1A8AaCHei+SFStx9qJz70oUfEAnHboPOmvOOl0IJZD101+spLA8n9jOd5uEChfe5r Mg/g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1782734247; x=1783339047; h=message-id:date:mime-version:subject:cc:to:from:x-gm-gg :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=2IkBnUkKy2XxZrEIuYpIqfqQ1xaokQJlPanTzI+zHG0=; b=j8Ky6S8BGmRjrwV8iMcZ6Rnr+8cngSTmgxZNpx+QiH8D+ZCbDWUFop/Wv3k3zfxFm6 6TkZskn52kYUDs7Y1vpqfRa5ZtGTtXjXgFJqSgLVeDyLOYhtrSJBec1PDzP9UiUGHI+R 8K7QVtqYVI1VS29D9y791izI7OVYTopa09NhGO1t2sNmwvAjiQjOyxsQ/a0VPDo7ypLx aBsFeClja99H2qkQyPNCCvzCWkL8BpT0HScMsfel5YXzl8/DdF8R0/9+qP8GuOcKXwNI 5J0afmzl8YAlownz49frSPr0YbZWIryG9y3VJl1r9xatOK/59p7h+uvsIxSd3BdOjpLF YUuw== X-Gm-Message-State: AOJu0Yws1pns3BsZDIO1XcXpi4yP7GLfvsYDfCSEProI5/q0MfgA+peA Ps90W+zDDtPg4pvuC2MCmOFn9YqRHnojdV4B/PBmeBlrmFor6Icr0PR6Qby9WGgU7dxOJZMoy7r 6BBKjD80= X-Gm-Gg: AfdE7cmPbjI3FiSIaNlijrGpbaymd/0zh79bZyvZVvnGVomUjN5k4KWaIpHkYA0bWA/ OSBu1cDNqBd/FSo1iObIzwH3R3yX32wwN7JWF+9ACGg8dC3CKg46qphhD91Ng12/8JudgPMq1h0 wyLeo6a/m2224efcSlPKdmJs9fDetBOGP21WnIV8JHBaf3UYmteYyYQu/7Te1VXjoHBWDokD/XS XlSQwBTUYvjn5M7hhIRtVqcnmED/RHbYwhpcl5eTomBp0wVWKAt368ZdtEAhj/Q0m12AVW+3nKZ pW4saoWiFtqxJqjaEGTgJUPDj3l6yM+LSuIUGEJEHXjUErhdh/u9DJ9tewTK0JGfThSYiqvv16b oUzV8PIkRykF50GTkA8wx0bmKjkPjFcSzbCN9bpKGisuIOvbriEJ3Ik7Na5jumLgtxALC70lDev 3E7ydiuXfbKTovvulwrUgxDTyUjQ== X-Received: by 2002:a05:600c:5249:b0:492:409d:b7c3 with SMTP id 5b1f17b1804b1-493b7197586mr6357495e9.13.1782734247434; Mon, 29 Jun 2026 04:57:27 -0700 (PDT) Received: from localhost (109-81-168-148.rct.o2.cz. [109.81.168.148]) by smtp.gmail.com with ESMTPSA id 5b1f17b1804b1-492690168d5sm426883825e9.14.2026.06.29.04.57.26 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 29 Jun 2026 04:57:27 -0700 (PDT) From: Antonin Houska To: pgsql-hackers@lists.postgresql.org CC: bharath.rupireddyforpostgres@gmail.com, mihailnikalayeu@gmail.com, adam8157@gmail.com Subject: Allow progress tracking of sub-commands X-Mailer: MH-E 8.6+git; nmh 1.8; GNU Emacs 28.3 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" Date: Mon, 29 Jun 2026 13:57:26 +0200 Message-ID: <106920.1782734246@localhost> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --=-=-= Content-Type: text/plain I've noticed several complaints about two commands trying to report their progress at the same time, overwriting each other's output [1][2][3]. I posted a prototype of an enhancement of the monitoring infrastructure that allows for progress reporting of two commands w/o conflicts [4]. This is a new version that passes regression tests. I'll register it for the upcoming CF. [1] https://www.postgresql.org/message-id/5667.1774513434%40localhost [2] https://www.postgresql.org/message-id/CALj2ACUgwSchK6jQ2CdKLBWUADTOE_zKdTff2Zg3E6hOuXKv-w%40mail.gmail.com [3] https://www.postgresql.org/message-id/aj4gJQMba0kClQmj%40Mac [4] https://www.postgresql.org/message-id/30939.1777888333%40localhost -- Antonin Houska Web: https://www.cybertec-postgresql.com --=-=-= Content-Type: text/x-diff Content-Disposition: attachment; filename=v01-0001-Allow-progress-tracking-of-sub-commands.patch