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 1rixuM-002gyO-SB for pgsql-www@arkaria.postgresql.org; Sat, 09 Mar 2024 14:42:43 +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 1rixuL-000qYu-He for pgsql-www@arkaria.postgresql.org; Sat, 09 Mar 2024 14:42:42 +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 1rixuL-000qYg-Ay for pgsql-www@lists.postgresql.org; Sat, 09 Mar 2024 14:42:41 +0000 Received: from mail-ua1-x936.google.com ([2607:f8b0:4864:20::936]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rixuE-003ci3-5o for pgsql-www@postgresql.org; Sat, 09 Mar 2024 14:42:40 +0000 Received: by mail-ua1-x936.google.com with SMTP id a1e0cc1a2514c-7db4484672bso1073676241.3 for ; Sat, 09 Mar 2024 06:42:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=xzilla-net.20230601.gappssmtp.com; s=20230601; t=1709995352; x=1710600152; darn=postgresql.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=eDN1XC5PRUG+zN+DRdb3E2QtJi9rdQCwlcFufNpm1Mw=; b=O5UuQzQ9wKvi3IqtQdwuP0FZ1DufSfN0Ors25wFm+IcF7gvFYRpDiS2T7h0YrISvIW fze64ft8rTxHUvZCIhEQecBr1dl7XH/130b+dBNTHD4VDmSeWhxEhQpOnSUUYPR/IRdb FOPcbExzxq6BfDXrJuxJkIj+mQZAnQ3XE7t5MNp9J47hd7GO5K4huUkOCSEUoQtrh/PE ALyl2UPoN1DfZiyCC1c2Koi8h+7+QD7ReNs1Vg78UVyINrdUxzlwDR83MBb25HqrJ+Cz fgM7SFUd59Z7wJ0Ru6XT3yO9D6SWy2RRSd8ASduWv6epUdnFpymaUwI6iy2kbOcCu8iD O9Lg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1709995352; x=1710600152; h=content-transfer-encoding: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=eDN1XC5PRUG+zN+DRdb3E2QtJi9rdQCwlcFufNpm1Mw=; b=xJpbp7DqE3YMoitEIgere8r9vcB9FI9kDP4ZYp8e5E/JeoEFf4Nb+c1Mu5mvMX7dMn Sl0GTw2GnrE1OowthgKSwzuUCO+3zU5nRUgreEUjTfMplcDFr0+/KE53jSU/lSj6yYFm 9e8t+s+E/xlVtoqfkMma60xN00R3J0AocM54DWT+TC5J401Nh7jSSJLgn1MtnqiZFn3/ I/SvGxr4qqpbaFxc1VPRLqu0YZTqJ5TBS5kLnxlqiL1Yg69w4HnBkLQmy8LBYQO+PkTG V5OsTnCxGAYKxyyzSl9nWL/wEz6k5LVNdl1t8gxANF1vToLaD2CU7rwofoqib8wuKDIb Ythw== X-Forwarded-Encrypted: i=1; AJvYcCXbFV0Z2dHj167nPbI0YuikmGbrrJPwJgyug54h/Jpw8WdL2gsMq+gwfE+FRt+KFq+/pzuna+/TtIqv8fOo4Wdto7gl0Wcqu9s= X-Gm-Message-State: AOJu0Yw03qG5HwpsRZNO+OOOFPl2dZVyuniMc7kJE72A+E+5gYkKDxDt DI/lnYz0dn3Q15XlCfZ2bVUCL79TttWRDuSlaJcpr+A8XPjIq+ZSEbXcbuANA+n1jho45m0U91+ +pLnpdVUyvqSuAe+1d27TQudSL5YOj3+cfc0LIQ== X-Google-Smtp-Source: AGHT+IGm1mGMVdJKfzQ4AU5fwYiz94eh6ly0O+7K2/1IgLV019No6eXwF5JDszNmJYQN1btCH/WTl0yz90mkHe2V/e0= X-Received: by 2002:a05:6102:2439:b0:472:682a:ae64 with SMTP id l25-20020a056102243900b00472682aae64mr840232vsi.31.1709995352390; Sat, 09 Mar 2024 06:42:32 -0800 (PST) MIME-Version: 1.0 References: <202403071419.jrbmk77bhelu@alvherre.pgsql> In-Reply-To: <202403071419.jrbmk77bhelu@alvherre.pgsql> From: Robert Treat Date: Sat, 9 Mar 2024 09:42:21 -0500 Message-ID: Subject: Re: Ask about bug numbering rules in pgsql-bugs mailing list To: Alvaro Herrera Cc: Jiangshan Liu , pgsql-www@postgresql.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Thu, Mar 7, 2024 at 9:19=E2=80=AFAM Alvaro Herrera wrote: > > On 2024-Mar-07, Jiangshan Liu wrote: > > > Hello! > > I'm writing my thesis expecting to refer to commit issues on the Postgr= eSQL website pgsql-bugs mailing list via bug numbering, but I'm concerned t= hat some of the commit issues are not numbered (e.g., https://www.postgresq= l.org/message-id/flat/1958255.PYKUYFuaPT%40aivenlaptop#1bdd1e237c4858f85b03= 13522c6bad2c ), and I'm curious about this, so I'd like to ask you for wha= t reason this is happening, please! Thank you > > We have a web interface to report bugs, which assigns numbers to them; > this interface simply copies the text to an email to the pgsql-bugs > mailing list, including the assigned number. However, many bugs are > reported not via the web interface but instead by direct email to the > same pgsql-bugs mailing list or even to another one (frequently > pgsql-hackers, but others too); these do not get any number. That's > exactly what happened in the case you quote. > > We don't have a central bug tracking system. > That said, it is still quite possible to track bugs in Postgres; simple even. https://twitter.com/robtreat2/status/1556991088912654337 Robert Treat https://xzilla.net