Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hBGCW-0000BU-Jo for pgsql-bugs@arkaria.postgresql.org; Tue, 02 Apr 2019 09:59:28 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hBGCU-0007FQ-77 for pgsql-bugs@arkaria.postgresql.org; Tue, 02 Apr 2019 09:59:26 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hBGCT-0007FJ-B6 for pgsql-bugs@lists.postgresql.org; Tue, 02 Apr 2019 09:59:26 +0000 Received: from sonic304-21.consmr.mail.ir2.yahoo.com ([77.238.179.146]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hBGCQ-0006cg-2m for pgsql-bugs@lists.postgresql.org; Tue, 02 Apr 2019 09:59:23 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.fr; s=s2048; t=1554199159; bh=qp9TSxyzfBPgouN4soaGdvV68+PIZsMkMADL5ZRn7Gg=; h=Date:From:To:Cc:In-Reply-To:References:Subject:From:Subject; b=LiCep1IHtn9pE9MQ7rxhEPes2umqljCUv2tRDNHoTt6iUVWFAMHVO5/Wz5fMrVKF52kNa5A3oJ9l7pjXn3RKt9buMv/WbNhxKCMKRUeNn08+AvEc8fAlIzfvolezyFBrPynbTnJTYvk4zO6DraJHqwRDTWGGwkuEHcjfOhFIV/CeSZtZDYs2FrL9D9LoDARdINLKL2LlkBPZH0lm0F+47KWtMglSn/Gf1TOeq1mqb8CZZLbW5/IZUuLvqYKOxsktLnIn0k0eG+iVs+jYzTWRoHSuCF9k1vqjc4OyvT9bhwfjFT9gBzZNRFdPPPY6NZn8qUnXysKLIiXWda6njnriJw== X-YMail-OSG: l_wNB6gVM1l48.E0WAkjjby8cAs1jDK4NqYiPAG66zDA3uxBtEYjKVPBXfPsnuf YBa_G.2YFo_v6dgb3aA0lx7IGaJo7LSnfkON04euXbfdbyrQnneeshpHN3NIkA1rfh8S3zrU52WX DPxyxNOtZrzRAJnOomr.EJKTTErZy7Cn2n778MPkJBxDwZeHj1LDZa1PVbECpy35AUCDo.3to3mJ XO4lyVcFdo7HY00XjERo2VbLtfuWZyOieK42pVRiysZZqoGYSOloiqSVQ70lGEPm9I3h70ifb0tS 3OhZ06WAzdg1hKTa_mP5Ma1YutcX8hqsj6EdQ4RPJli6XFViFkbn7bL3yIS1C8DrsN7jzrMfxE9i Qkhqysdmw4uk0hiQP8mEA2KCelSRGGDCiV0FVMzKul0N0C5UjmI5dUeQST_9kLdpIu.PYghMZgUH z0BSH9fU3yDw8nZEu7zRvkcwwF6tvO32XLh041TP2G1VHP78MXVayZ2OhmbYPnLxm.F62dkoDy4H iVIUo7DczZunrgQx5aI0FoLKheFz_YTj5UD55Sv2tHRLd6MkcpqrFCElk8UU1J6Q6FVvqKqaEaFK xxH8vOgFkpbyJeX05.vzvKpMqo7oErXaXTvhY4PLPt9SJMJutu3AIyHCgJvRObilLzNGBZQ49OUa _5Yh8X215Dq23H5802Xq6fXYy.DhxW9oB.2ou1sMCqbdNYbs9ecWAwVYhgAE_LhaEEnZzDYKfWzA JncPmYZvJDPI3r4AHrHAs7CGqrNM2xv9V7nBVhf3Bu.n6jSA27sCUJyvO2_UEJiSvmvYNeZ8KsHD c5Kl40_xn96qwiAFgErDmlam95rTZMSQyCGvV2bPcSKdst9YHXI3C63dNTtlUkrw1KV10h.wCRyN zznJCZ8RiKnitRX.q.ImXCDosWsHRhV1VgFcvYsRAiK.RXOErAPHPgW4_KrvpTPm5QP6MjL2fg7f jICrT3iQL6yo9yPhdrjU8NMX00ApBc0KkYflxrRVI0yKvgasHv2MvyULJsADIAzX6XQay3u6R2ek sv7OSYNeAKNPmccoHycfUpW_m_KijC4XhrRlc7JlE6BBvOrN5MlRsh6TDQi0x2.9fSsLXoWsCAGy iUG8gOm38ePI- Received: from sonic.gate.mail.ne1.yahoo.com by sonic304.consmr.mail.ir2.yahoo.com with HTTP; Tue, 2 Apr 2019 09:59:19 +0000 Date: Tue, 2 Apr 2019 09:59:14 +0000 (UTC) From: ANASTACIO Tiago To: Thomas Munro , Peter Geoghegan Cc: PostgreSQL mailing lists Message-ID: <1831482307.24522245.1554199154256@mail.yahoo.com> In-Reply-To: References: <15726-6d67e4fa14f027b3@postgresql.org> Subject: Re: BUG #15726: parallel queries failed ERROR: invalid name syntax CONTEXT: parallel worker MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_24522244_1773210958.1554199154254" X-Mailer: WebService/1.1.13212 YMailNorrin Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.0) Gecko/20100101 Firefox/60.0 Content-Length: 4089 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk ------=_Part_24522244_1773210958.1554199154254 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Thank you guys. I fixed the parameter and it worked. A pity background worker are no more verbose (DEBUG5) than: 2019-04-02 09:42:38.993 GMT [17654] ERROR:=C2=A0 invalid name syntax About TracingI used strace and grep background woker pid. But I didn't get = that trace, which tool did you use ? Le mardi 2 avril 2019 =C3=A0 02:41:40 UTC+2, Peter Geoghegan a =C3=A9crit : =20 =20 >On Mon, Apr 1, 2019 at 5:33 PM Thomas Munro wrot= e: >> Erm -- obviously that BEGIN was unnecessary and you see the error >> without it.=C2=A0 Anyway, the point I was making is that you don't get a= n >> error if you set it in postgresql.conf, but you do if you set it in >> other contexts, including the parallel worker startup sequence.=C2=A0 I >> wondered if this might have been a consequence of the parallel startup>>= reordering that happened with commit 6c3c9d41, but nope -- >> RestoreGUCState() was always run inside a transaction. >I wonder if this known issue is relevant here: >https://www.postgresql.org/message-id/20153.1523471686%40sss.pgh.pa.us >--=20 >Peter Geoghegan =20 ------=_Part_24522244_1773210958.1554199154254 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Thank you guys. I fixed the parameter and it worked.

A pity background worker are no more verbose (DEBUG5) than:=

2019-04-02 09:42:38.993 GMT [17654] ERROR:&= nbsp; invalid name syntax

About Tracing
I used= strace and grep background woker pid. But I didn't get that trace, which t= ool did you use ?


=20
=20
Le mardi 2 avril 2019 =C3=A0 02:41:40 UTC+2, Peter Geog= hegan <pg@bowt.ie> a =C3=A9crit :


>On Mon, Apr 1, 2019 at 5:33 PM Th= omas Munro <thomas.munro@gmail.com> wrote:

>> Erm -- obviously that BEGIN was unnecessary and you see the= error
>> without it.  Anyway, the point I was= making is that you don't get an
>> error if you se= t it in postgresql.conf, but you do if you set it in
>= > other contexts, including the parallel worker startup sequence.  = I

>> wondered if this might hav= e been a consequence of the parallel startup
>> reordering that = happened with commit 6c3c9d41, but nope --
>> Resto= reGUCState() was always run inside a transaction.

<= br clear=3D"none">>I wonder if this known issue is relevant here:

>https://www.postgresql.org/message-id/20153.1523471686%40= sss.pgh.pa.us

>--
>Peter Geoghegan

------=_Part_24522244_1773210958.1554199154254--