pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: tsunakawa.takay@fujitsu.com <tsunakawa.takay@fujitsu.com>
Cc: k.jamison@fujitsu.com <k.jamison@fujitsu.com>
Cc: iwata.aya@fujitsu.com <iwata.aya@fujitsu.com>
Cc: 'pgsql-hackers@lists.postgresql.org' <pgsql-hackers@lists.postgresql.org>
Subject: Re: libpq debug log
Date: Tue, 2 Feb 2021 11:20:45 -0300
Message-ID: <20210202142045.GA13771@alvherre.pgsql> (raw)
In-Reply-To: <OSBPR01MB2982F69F3DB120516221E7E9FEB99@OSBPR01MB2982.jpnprd01.prod.outlook.com>

On 2021-Jan-29, tsunakawa.takay@fujitsu.com wrote:

> (30)
> +/*
> + * Deallocate FE/BE message tracking memory.  We only do this because
> + * FE message can grow arbitrarily large, and skip it in the initial state,
> + * because it's likely pointless.
> + */
> +void
> +pqTraceUninit(PGconn *conn)
> +{
> +	if (conn->fe_msg &&
> +		conn->fe_msg->num_fields != DEF_FE_MSGFIELDS)
> +	{
> +		free(conn->fe_msg);
> +		conn->fe_msg = NULL;
> +	}
> 
> What does the second if condition mean?  If it's not necessary, change the comment accordingly.

The rationale for that second condition is this: if the memory allocated
is the initial size, we don't free memory, because it would just be
allocated of the same size next time, and that size is not very big, so
it's not a big deal if we just let it be, so that it is reused if we
call PQtrace() again later.  However, if the allocated size is larger
than default, then it is possible that some previous tracing run has
enlarged the trace struct to a very large amount of memory, and we don't
want to leave that in place.

-- 
Álvaro Herrera       Valdivia, Chile





view thread (234+ messages)  latest in thread

Message-ID: <20210202142045.GA13771@alvherre.pgsql>
Permalink:  ../20210202142045.GA13771@alvherre.pgsql/
Also on:    postgresql.org/message-id/20210202142045.GA13771@alvherre.pgsql

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: alvherre@alvh.no-ip.org, tsunakawa.takay@fujitsu.com, k.jamison@fujitsu.com, iwata.aya@fujitsu.com, pgsql-hackers@lists.postgresql.org
  Subject: Re: libpq debug log
  In-Reply-To: <20210202142045.GA13771@alvherre.pgsql>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox