Received: from sss2.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2])
	by hub.org (8.10.1/8.10.1) with ESMTP id e5RLb0137774
	for <pgsql-interfaces@postgresql.org>;
	Tue, 27 Jun 2000 17:37:01 -0400 (EDT)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss2.sss.pgh.pa.us (8.9.3/8.9.3) with ESMTP id RAA14367;
	Tue, 27 Jun 2000 17:36:57 -0400 (EDT)
To: "Robert A. Knop Jr." <rknop@lilys.lbl.gov>
cc: pgsql-interfaces@postgresql.org
Subject: Re: libpq & freeing character results 
In-reply-to: <Pine.LNX.4.10.10006271204130.1921-100000@lilys.lbl.gov> 
References: <Pine.LNX.4.10.10006271204130.1921-100000@lilys.lbl.gov>
Comments: In-reply-to "Robert A. Knop Jr." <rknop@lilys.lbl.gov>
	message dated "Tue, 27 Jun 2000 12:06:44 -0700"
Date: Tue, 27 Jun 2000 17:36:57 -0400
Message-ID: <14360.962141817@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Archive-Number: 200006/108

"Robert A. Knop Jr." <rknop@lilys.lbl.gov> writes:
> If one uses libpq functions such as PQfname, should one free the returned
> character string?

No.  Unless the doc for the function explicitly says you should free
its result, it's a pointer into libpq-managed space.

			regards, tom lane