Subject tag lowercase - Mailing list pgsql-www

I still have received no feedback on why the subject line sometimes has
"[pgsql-patches]" instead of "[PATCHES]".  Sample below.

Also, don't we have filters to block emails with the subject
"unsubscribe"?  I just saw one on the admin list.

---------------------------------------------------------------------------

----- Forwarded message from korryd@enterprisedb.com -----

X-Greylist: domain auto-whitelisted by SQLgrey-1.7.4
thread-index: AcdFiOEEhe23MX+pRO+bHDV6ruYJbw==
Subject: Re: [pgsql-patches] Patch to avoid gprof profiling overwrites
Content-Class: urn:content-classes:message
Importance: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2826
From: <korryd@enterprisedb.com>
To: Bruce Momjian <bruce@momjian.us>
cc: <pgsql-patches@postgresql.org>
In-Reply-To: <200701312202.l0VM21o26921@momjian.us>
References: <200701312202.l0VM21o26921@momjian.us>
Date: Wed, 31 Jan 2007 17:59:21 -0500
Message-ID: <1170284361.6941.115.camel@sakai.localdomain>
X-Mailer: Evolution 2.4.0 
X-OriginalArrivalTime: 31 Jan 2007 22:40:57.0359 (UTC) FILETIME=[DFA8A9F0:01C74588]
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=0.624 tagged_above=0 required=5 tests=AWL, BAYES_40,HTML_MESSAGE, NO_REAL_NAME, SPF_PASS
X-Spam-Level: 
X-Mailing-List: pgsql-patches
List-Archive: <http://archives.postgresql.org/pgsql-patches>
List-Help: <mailto:majordomo@postgresql.org?body=help>
List-Id: <pgsql-patches.postgresql.org>
List-Owner: <mailto:pgsql-patches-owner@postgresql.org>
List-Post: <mailto:pgsql-patches@postgresql.org>
List-Subscribe: <mailto:majordomo@postgresql.org?body=sub%20pgsql-patches>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-patches>
Precedence: bulk
Sender: pgsql-patches-owner@postgresql.org

> And the patch is where?


You caught me; guess I'd better make something up fast, huh?

Here it is, thanks.
           -- Korry


> 
> ---------------------------------------------------------------------------
> 
> korryd@enterprisedb.com wrote:
> > It's difficult to profile a backend server process  (using gprof)
> > because each process overwrites any earlier profile as it exits.
> > 
> > It is especially tricky to nab a useful profile if you happen to have
> > autovacuum enabled.
> > 
> > This patch reduces the problem by forcing the backend to 'cd' to a new
> > directory ($PGDATA/gprof/pid) just before calling exit(), but only if
> > the backend was compiled with -DLINUX_PROFILE.
> > 
> > I've tested this with Linux, but not with other host architectures. 
> > 
> >         -- Korry
> > 
> > 
> > 
> > --
> >   Korry Douglas    korryd@enterprisedb.com
> >   EnterpriseDB      http://www.enterprisedb.com
> 



-- Korry Douglas    korryd@enterprisedb.com EnterpriseDB      http://www.enterprisedb.com

[ Attachment, skipping... ]


---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate      subscribe-nomail command to
majordomo@postgresql.orgso that your      message can get through to the mailing list cleanly
 
----- End of forwarded message from korryd@enterprisedb.com -----

--  Bruce Momjian   bruce@momjian.us EnterpriseDB    http://www.enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +