Received: from localhost (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id A8D4F634241 for ; Wed, 13 Jan 2010 11:55:35 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024) with ESMTP id 05240-02-7 for ; Wed, 13 Jan 2010 15:55:15 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.25]) by mail.postgresql.org (Postfix) with ESMTP id 5EC55633F57 for ; Wed, 13 Jan 2010 11:54:02 -0400 (AST) Received: by ey-out-2122.google.com with SMTP id 22so4080320eye.33 for ; Wed, 13 Jan 2010 07:53:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=v4mxo7YjyyAw2gBuT3ci2i1vc+Ye+g82EDzAhdxbYFQ=; b=ZvfEd0fdJYWZbnQvan/nPHTYPyZa2CB71hzbvvzyJOv5rEdJZKsdXW3tTqe2cVMWc6 +eNyoiM08e+POszjQqxfMygncdLFhfoPtNpnVnm7i74RwQvYv7i729Y+v23IMYhiCNI7 v6Huva4VG9foY9BPnAvHHvZ7XCtn/w0nrqKAA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=Iy4nzPIus3R5JRKw1TCbXbieVX7a7BiqPnss8nDAERLHNaAdYNfjgtp9WgVLoqMK7Q iUzsEwQpZfCwOUZbXa0pZZXpgnTmuiwgTEcnnxP5BgZZsk3mWCW8N/qO/Abhj9uD7FTG Wx8OJ7O1yHWcypu0U9Fx1Npt/2RCnhoflCaMU= MIME-Version: 1.0 Received: by 10.213.100.156 with SMTP id y28mr10204139ebn.68.1263398039831; Wed, 13 Jan 2010 07:53:59 -0800 (PST) In-Reply-To: <4B4DD381.6070302@timbira.com> References: <4B4D5698.8040808@emolecules.com> <4B4D78B2.30600@2ndquadrant.com> <4B4DD381.6070302@timbira.com> Date: Wed, 13 Jan 2010 12:53:59 -0300 Message-ID: Subject: Re: a heavy duty operation on an "unused" table kills my server From: Eduardo Piombino To: Euler Taveira de Oliveira Cc: Greg Smith , Craig James , pgsql-performance@postgresql.org Content-Type: multipart/alternative; boundary=001636c5bc3f5fc545047d0dc7eb X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.598 tagged_above=-10 required=5 tests=BAYES_00=-2.599, HTML_MESSAGE=0.001 X-Spam-Level: X-Archive-Number: 201001/251 X-Sequence-Number: 37131 --001636c5bc3f5fc545047d0dc7eb Content-Type: text/plain; charset=ISO-8859-1 With that said, I assume my current version of pgsql DOES make all this heavy work go through WAL logging. Curious thing is that I remember (of course) reviewing logs of the crash times, and I didn't see anything strange, not even the famous warning "you are making checkpoints too often. maybe you should consider using extending the checkpoint_segments parameter". I will check it again. Besides, I will try to gather as much information on the system itself (RAID controllers, disk vendors, etc). Thank you, will keep you posted. On Wed, Jan 13, 2010 at 11:06 AM, Euler Taveira de Oliveira < euler@timbira.com> wrote: > Eduardo Piombino escreveu: > > Maybe it does not get logged at all until the ALTER is completed? > > > This feature [1] was implemented a few months ago and it will be available > only in the next PostgreSQL version (8.5). > > [1] http://archives.postgresql.org/pgsql-committers/2009-11/msg00018.php > > > -- > Euler Taveira de Oliveira > http://www.timbira.com/ > --001636c5bc3f5fc545047d0dc7eb Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable With that said, I assume my current version of pgsql DOES make all this hea= vy work go through WAL logging.

Curious thing is that I remember (of= course) reviewing logs of the crash times, and I didn't see anything s= trange, not even the famous warning "you are making checkpoints too of= ten. maybe you should consider using extending the checkpoint_segments para= meter".

I will check it again.
Besides, I will try to gather as much informa= tion on the system itself (RAID controllers, disk vendors, etc).
Thank y= ou, will keep you posted.

On Wed, Jan 13,= 2010 at 11:06 AM, Euler Taveira de Oliveira <euler@timbira.com> wrote:
Eduardo Piombino = escreveu:
> Maybe it does not get logged at all until the ALTER = is completed?
>
This feature [1] was implemented a few months ago and it will be avai= lable
only in the next PostgreSQL version (8.5).

[1] http://archives.postgresql.org/pgsql-committers= /2009-11/msg00018.php


--
=A0Euler Taveira de Oliveira
=A0http://www.timbir= a.com/

--001636c5bc3f5fc545047d0dc7eb--