pgsql: Change ps_status.c to explicitly track the current logical length

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Change ps_status.c to explicitly track the current logical length
Date: 2010-05-27 19:20:16
Message-ID: 20100527192016.E07E57541D3@cvs.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Log Message:
-----------
Change ps_status.c to explicitly track the current logical length of ps_buffer.
This saves cycles in get_ps_display() on many popular platforms, and more
importantly ensures that get_ps_display() will correctly return an empty
string if init_ps_display() hasn't been called yet. Per trouble report
from Ray Stell, in which log_line_prefix %i produced junk early in backend
startup.

Back-patch to 8.0. 7.4 doesn't have %i and its version of get_ps_display()
makes no pretense of avoiding pad junk anyhow.

Tags:
----
REL8_0_STABLE

Modified Files:
--------------
pgsql/src/backend/utils/misc:
ps_status.c (r1.23.4.1 -> r1.23.4.2)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/misc/ps_status.c?r1=1.23.4.1&r2=1.23.4.2)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2010-05-28 01:14:03 pgsql: Rejigger mergejoin logic so that a tuple with a null in the first
Previous Message Tom Lane 2010-05-27 19:20:06 pgsql: Change ps_status.c to explicitly track the current logical length