Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 3605A9FB308 for ; Wed, 31 Jan 2007 19:25:09 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-new, port 10024) with ESMTP id 21297-06 for ; Wed, 31 Jan 2007 19:24:50 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from momjian.us (momjian.us [70.90.9.53]) by postgresql.org (Postfix) with ESMTP id 0820B9FB27D for ; Wed, 31 Jan 2007 19:24:53 -0400 (AST) Received: (from bruce@localhost) by momjian.us (8.11.6/8.11.6) id l0VNOtL27431; Wed, 31 Jan 2007 18:24:55 -0500 (EST) From: Bruce Momjian Message-Id: <200701312324.l0VNOtL27431@momjian.us> Subject: Subject tag lowercase To: PostgreSQL www Date: Wed, 31 Jan 2007 18:24:54 -0500 (EST) CC: "Marc G. Fournier" X-Mailer: ELM [version 2.4ME+ PL123] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="US-ASCII" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200701/136 X-Sequence-Number: 11403 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: To: Bruce Momjian cc: 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: List-Help: List-Id: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: 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.org so 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. +