Date: Thu, 16 Sep 2021 19:29:14 +0200 (CEST)
From: Andreas Joseph Krogh <andreas@visena.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Peter Eisentraut <peter.eisentraut@enterprisedb.com>,
	Andrew Dunstan <andrew@dunslane.net>,
	torikoshia <torikoshia@oss.nttdata.com>,
	Pgsql Hackers <pgsql-hackers@postgresql.org>
Message-ID: <VisenaEmail.8.1b1e56356ccc8dba.17bef8e00ad@tc7-visena>
In-Reply-To: <1239278.1631811459@sss.pgh.pa.us>
References: <5bafa66ad529e11860339565c9e7c166@oss.nttdata.com>
 <3208199.1631039493@sss.pgh.pa.us>
 <b6fecc71-60b9-bd44-4b78-f2a9dd74f46f@enterprisedb.com>
 <d70fa4dfd333b1de1024e50c2ad1a6ea@oss.nttdata.com>
 <24ce73f9-c714-9a7c-6cc0-34e724c8f1c9@dunslane.net>
 <984394.1631719708@sss.pgh.pa.us> <1126187.1631749231@sss.pgh.pa.us>
 <VisenaEmail.1.95a6771aba78f64b.17bef3943f0@tc7-visena>
 <1239278.1631811459@sss.pgh.pa.us>
Subject: Re: EXPLAIN(VERBOSE) to CTE with SEARCH BREADTH FIRST fails
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_Part_15860_889134084.1631813354825"
Archived-At: 
 <https://www.postgresql.org/message-id/VisenaEmail.8.1b1e56356ccc8dba.17bef8e00ad%40tc7-visena>
Precedence: bulk

------=_Part_15860_889134084.1631813354825
Content-Type: multipart/related;
	boundary="----=_Part_15861_786841647.1631813354825"

------=_Part_15861_786841647.1631813354825
Content-Type: multipart/alternative;
	boundary="----=_Part_15862_453346517.1631813354843"

------=_Part_15862_453346517.1631813354843
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable


P=C3=A5 torsdag 16. september 2021 kl. 18:57:39, skrev Tom Lane <tgl@sss.pg=
h.pa.us=20
<mailto:tgl@sss.pgh.pa.us>>:=20
[...]
 > FWIW; I saw this Open Item was set to fixed, but I'm still getting this=
=20
error
 > in 388726753b638fb9938883bdd057b2ffe6f950f5

 The open item was not about that parser shortcoming, nor did this patch
 claim to fix it.

 regards, tom lane=20

Ok, sorry for the noise.=20


--
 Andreas Joseph Krogh=20
------=_Part_15862_453346517.1631813354843
Content-Type: text/html;charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div>P=C3=A5 torsdag 16. september 2021 kl. 18:57:39, skrev Tom Lane &lt;<a=
 href=3D"mailto:tgl@sss.pgh.pa.us">tgl@sss.pgh.pa.us</a>&gt;:</div>

<blockquote style=3D"border-left: 1px solid rgb(204, 204, 204); margin: 0pt=
 0pt 0pt 0.8ex; padding-left: 1ex;">
<div style=3D"display:inline; font-family: monospace; font-size: 12px;">[..=
.]<br>
&gt; FWIW; I saw this Open Item was set to fixed, but I'm still getting thi=
s error<br>
&gt; in 388726753b638fb9938883bdd057b2ffe6f950f5<br>
<br>
The open item was not about that parser shortcoming, nor did this patch<br>
claim to fix it.<br>
<br>
regards, tom lane</div>
</blockquote>

<div>=C2=A0</div>

<div>Ok, sorry for the noise.</div>

<div class=3D"visena-email-signature" data-visena-message-id=3D"&lt;VisenaE=
mail.8.1b1e56356ccc8dba.17bef8e00ad@tc7-visena>">
<div>
<div>=C2=A0</div>

<div>--<br>
Andreas Joseph Krogh</div>
</div>
</div>
------=_Part_15862_453346517.1631813354843--

------=_Part_15861_786841647.1631813354825--

------=_Part_15860_889134084.1631813354825--