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 1kS9aE-0006Ap-QC for pgsql-bugs@arkaria.postgresql.org; Tue, 13 Oct 2020 01:58:34 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kS9aD-0004MA-Jp for pgsql-bugs@arkaria.postgresql.org; Tue, 13 Oct 2020 01:58:33 +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 1kS9aD-0004M3-Dt for pgsql-bugs@lists.postgresql.org; Tue, 13 Oct 2020 01:58:33 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kS9a6-0006QI-VN for pgsql-bugs@lists.postgresql.org; Tue, 13 Oct 2020 01:58:32 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 09D1wPe33404269; Mon, 12 Oct 2020 21:58:25 -0400 From: Tom Lane To: Bryn Llewellyn cc: "David G. Johnston" , PostgreSQL mailing lists Subject: Re: Wrong results from function that selects from vier after "created or replace" In-reply-to: References: <4DE6C9D8-77A5-4858-82CB-18728F59D715@yugabyte.com> Comments: In-reply-to Bryn Llewellyn message dated "Mon, 12 Oct 2020 18:26:14 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <3404267.1602554304.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Mon, 12 Oct 2020 21:58:24 -0400 Message-ID: <3404268.1602554304@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Bryn Llewellyn writes: > I hadn=E2=80=99t realized that submitting a bug as the doc at www.postgr= esql.org/docs/12/bug-reporting.html seems to suggest is the recommended me= thod (=E2=80=9CIn general, send bug reports to the bug report mailing list= at =E2=80=A6=E2=80=9D) would _never_ res= ult in a bug being filed (even if it=E2=80=99s acknowledged to be a bug). = So thanks for that tip off! As far as that goes, the closest thing we have to an "official bug report" is an email to the pgsql-bugs mailing list --- which is what you've done. The only thing that webform does differently is attach a subject line with a serial number; but the subject line has little bearing on how we treat the report. As David indicated, what we usually use as a formal reference is the email's message ID, which can be used conveniently to index into the Postgres project's email archives. We do that in part because many bug reports arrive via other email lists. In this case, multiple people have opined that it isn't a bug, but you'd have gotten the exact same responses if you'd gone via the webform. regards, tom lane