public inbox for [email protected]
help / color / mirror / Atom feedFrom: Bruce Momjian <[email protected]>
To: PostgreSQL www <[email protected]>
Cc: Marc G. Fournier <[email protected]>
Subject: Subject tag lowercase
Date: Wed, 31 Jan 2007 18:24:54 -0500 (EST)
Message-ID: <[email protected]> (raw)
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 [email protected] -----
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: <[email protected]>
To: Bruce Momjian <[email protected]>
cc: <[email protected]>
In-Reply-To: <[email protected]>
References: <[email protected]>
Date: Wed, 31 Jan 2007 17:59:21 -0500
Message-ID: <[email protected]>
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:[email protected]?body=help>
List-Id: <pgsql-patches.postgresql.org>
List-Owner: <mailto:[email protected]>
List-Post: <mailto:[email protected]>
List-Subscribe: <mailto:[email protected]?body=sub%20pgsql-patches>
List-Unsubscribe: <mailto:[email protected]?body=unsub%20pgsql-patches>
Precedence: bulk
Sender: [email protected]
> And the patch is where?
You caught me; guess I'd better make something up fast, huh?
Here it is, thanks.
-- Korry
>
> ---------------------------------------------------------------------------
>
> [email protected] 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 [email protected]
> > EnterpriseDB http://www.enterprisedb.com
>
--
Korry Douglas [email protected]
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 [email protected] so that your
message can get through to the mailing list cleanly
----- End of forwarded message from [email protected] -----
--
Bruce Momjian [email protected]
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
view thread (4+ messages) latest in thread
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: [email protected]
Cc: [email protected], [email protected]
Subject: Re: Subject tag lowercase
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox