Received: from malur.postgresql.org ([2a02:16a8:dc51::56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fPzjt-0004c0-Im for pgsql-docs@arkaria.postgresql.org; Tue, 05 Jun 2018 00:22:17 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fPzjr-0002iB-T7 for pgsql-docs@arkaria.postgresql.org; Tue, 05 Jun 2018 00:22:15 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fPzjr-0002i2-NH for pgsql-docs@lists.postgresql.org; Tue, 05 Jun 2018 00:22:15 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fPzjp-0005xk-0Y for pgsql-docs@lists.postgresql.org; Tue, 05 Jun 2018 00:22:15 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id w550MAII024819; Mon, 4 Jun 2018 20:22:10 -0400 From: Tom Lane To: Craig Ringer cc: duncan.reitboeck@gmail.com, pgsql-docs@lists.postgresql.org Subject: Re: Crash when using PQgetvalue In-reply-to: References: <152812598158.26719.17918140296757658987@wrigleys.postgresql.org> Comments: In-reply-to Craig Ringer message dated "Tue, 05 Jun 2018 07:57:52 +0800" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <24817.1528158130.1@sss.pgh.pa.us> Date: Mon, 04 Jun 2018 20:22:10 -0400 Message-ID: <24818.1528158130@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Craig Ringer writes: > On 4 June 2018 at 23:26, PG Doc comments form >> I am not sure if I am doing something wrong or there is a bug in the code >> but I am getting a strange issue. When I try to run the following code I >> get a crash when attempting to accessing the values using PQgetvalue. > This isn't really a comment on the documentation. Indeed. The submitter did file a bug a bit later, and we dealt with it over there. regards, tom lane