From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: [HACKERS] Overhead for stats_command_string et al, take 2 |
Date: | 2006-06-26 21:31:53 |
Message-ID: | 23191.1151357513@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Bruce Momjian <bruce(at)momjian(dot)us> writes:
> Attached patch adds GUC 'update_process_title' to control ps display
> updates per SQL command. Default to 'on'. GUC name OK?
This is an ugly patch. Why not *one* test of the GUC variable, inside
set_ps_display(), and no side-effects on callers? You would need to
force an initial update from init_ps_display, but that only requires a
small amount of code refactoring inside ps_status.c.
The one place that might be worth having an external test on the GUC is
in lock.c, but then it should bypass the entire business of copying,
modifying, and restoring the title ... not just the two set_ps_display
calls.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2006-06-26 21:36:14 | Re: Non-transactional pg_class, try 2 |
Previous Message | Tom Lane | 2006-06-26 21:26:33 | Re: [PATCHES] Non-transactional pg_class, try 2 |
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2006-06-26 21:36:14 | Re: Non-transactional pg_class, try 2 |
Previous Message | Tom Lane | 2006-06-26 21:26:33 | Re: [PATCHES] Non-transactional pg_class, try 2 |