Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 4BED337C02E for ; Tue, 30 Sep 2008 22:15:43 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 92769-05 for ; Tue, 30 Sep 2008 22:15:39 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.154]) by postgresql.org (Postfix) with ESMTP id BB93237C000 for ; Tue, 30 Sep 2008 22:15:39 -0300 (ADT) Received: by fg-out-1718.google.com with SMTP id 16so231180fgg.23 for ; Tue, 30 Sep 2008 18:15:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type:references; bh=ccavkAxIc2y0ydswO5nDl8rs8IGZqTolZq64k/jzF5I=; b=GeTAlE08kOWElVh4Efj/9qkMkmqGStHBzZm5YYHkHbd8neKXvQmVeUjRo7kE4kkQda wvF1pmjUdmmUBB7oeEzhR6wMbhBUIWpVAzk6RiJbUuqIuazvumIM1noeFhgJwmqeR9M8 2fu14uWaAKoVOyX9gmy/yErk5Cg/sveavlBMk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:references; b=u/YbtQSAhlCsr5x1PkCLqIC5BgXUEWkv3m2EjJWgp053lByk9Lz4UeLaPkc9MKIlXt ZbcugPM33rXkZ58Wydxtx32ftTw7zV2JC0bS1HxImcIIDCjrGLIqF7uWfwsXqVmBbvSV 50rYIO7jKIhzLsReOt4MMPaCwIKEDJ/eJxgg4= Received: by 10.86.79.19 with SMTP id c19mr6381930fgb.67.1222823737463; Tue, 30 Sep 2008 18:15:37 -0700 (PDT) Received: by 10.86.71.17 with HTTP; Tue, 30 Sep 2008 18:15:37 -0700 (PDT) Message-ID: <3a0028490809301815x2d019ff9l3a08d81840156b75@mail.gmail.com> Date: Tue, 30 Sep 2008 23:15:37 -0200 From: "Rafael Domiciano" To: "Steve Crawford" Subject: Re: What process clears the logs? Cc: "Carol Walter" , pgsql-admin@postgresql.org In-Reply-To: <48E2A10C.9060602@pinpointresearch.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_7215_15693311.1222823737453" References: <64D96E8A-8E58-458C-B299-8998112F88FA@indiana.edu> <48E27D72.9040409@pinpointresearch.com> <48E2A10C.9060602@pinpointresearch.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.001 tagged_above=0 required=5 tests=HTML_MESSAGE=0.001 X-Spam-Level: X-Archive-Number: 200809/362 X-Sequence-Number: 30455 ------=_Part_7215_15693311.1222823737453 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hello Carol, Maybe I'm thinking wrong, but I have a problem like yours; and I realize that the vacuum Freeze that does that work. I have read that somewhere in the net, that I don't remember now. To prevent that I created a proccess that run every night, that vacuums the database, and started the vacuum daemon. All machines I had problems are Slony-slaves. Best Regards, Rafael Domiciano Postgres DBA 2008/9/30 Steve Crawford > Carol Walter wrote: > >> Ah-h-h, that's exactly my question. What part of Postgres "takes care of >> this itself." I'm asking because I had 86 pg_clog files dated back to >> mid-May. I got the impression from something Tom said that backups should >> prune this directory. Perhaps my "impression" was wrong. Most databases >> I've used in the past have gotten rid of the transaction logs, etc, when a >> backup is done. The restore process used that last backup and then applied >> the transaction logs to it. Once another backup was completed the old >> transaction logs were no longer needed. I'm trying to understand what >> happens "under the hood" so to speak. What checkpoint_settings value are >> you referring to? >> > Sorry. I had a brain/fingers disconnect. I meant the "checkpoint_segments" > setting. Anyway, answers to a number of your questions regarding write-ahead > logging may be found here: > http://www.postgresql.org/docs/8.3/interactive/wal-configuration.html > > > Cheers, > Steve > > > -- > Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-admin > ------=_Part_7215_15693311.1222823737453 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline
Hello Carol,

Maybe I'm thinking wrong, but I have a problem like yours; and I realize that the vacuum Freeze that does that work.
I have read that somewhere in the net, that I don't remember now.

To prevent that I created a proccess that run every night, that vacuums the database, and started the vacuum daemon.
All machines I had problems are Slony-slaves.

Best Regards,

Rafael Domiciano
Postgres DBA

2008/9/30 Steve Crawford <scrawford@pinpointresearch.com>
Carol Walter wrote:
Ah-h-h, that's exactly my question.  What part of Postgres "takes care of this itself."  I'm asking because I had 86 pg_clog files dated back to mid-May.  I got the impression from something Tom said that backups should prune this directory.  Perhaps my "impression" was wrong.  Most databases I've used in the past have gotten rid of the transaction logs, etc, when a backup is done. The restore process used that last backup and then applied the transaction logs to it.  Once another backup was completed the old transaction logs were no longer needed.  I'm trying to understand what happens "under the hood" so to speak.  What checkpoint_settings value are you referring to?
Sorry. I had a brain/fingers disconnect. I meant the "checkpoint_segments" setting. Anyway, answers to a number of your questions regarding write-ahead logging may be found here:
http://www.postgresql.org/docs/8.3/interactive/wal-configuration.html


Cheers,
Steve


--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin

------=_Part_7215_15693311.1222823737453--