Received: from maia.hub.org (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id 0C0D963285B for ; Wed, 10 Feb 2010 20:51:44 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024) with ESMTP id 78631-01 for ; Thu, 11 Feb 2010 00:51:26 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-ew0-f209.google.com (mail-ew0-f209.google.com [209.85.219.209]) by mail.postgresql.org (Postfix) with ESMTP id 0CEB2632693 for ; Wed, 10 Feb 2010 20:51:32 -0400 (AST) Received: by ewy1 with SMTP id 1so115043ewy.34 for ; Wed, 10 Feb 2010 16:51:31 -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=ONgtGq/ZSttbN7g5Syfv5TD39c3kocRikSw/WYypTu8=; b=I+t0Cqpg0nzJGu3Q+0sprJXY9tllBgJm4VYfaQb340nHq8NgI3DpUBYl2JxbTRaDWp R6xmyalNxF+Pg3ydeJPnycJ3Mkj/SXdFPN0QPjemOi8nUTtTdWZKCtNOfBbpN2NR+kov 8Lg5bA/qOovxn+uK3jOzCosCWiQdg08w/9KLg= 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=IxwEJ+5uJy782g80kD0kyFlSCmqt9MgZzcNFmFp2pmv+2JbNB355eBslnh87GOpqQ0 IgBdxApb0lmVR9tL3544Rt7uWfN/JAzf1oA8Yi6WBVwrP23R+GiZi/QVnw7PK/4XI13V ETU/jkN0HECxiX9xdFwob5QvoTRYEhfkiZeKk= MIME-Version: 1.0 Received: by 10.216.86.129 with SMTP id w1mr622682wee.145.1265849491010; Wed, 10 Feb 2010 16:51:31 -0800 (PST) In-Reply-To: <7ac84c51002101609l190ec043s7fdde292969da457@mail.gmail.com> References: <7ac84c51002101530q59fa87c1w205fdf5243d9d69a@mail.gmail.com> <7ac84c51002101609l190ec043s7fdde292969da457@mail.gmail.com> Date: Wed, 10 Feb 2010 18:51:30 -0600 Message-ID: Subject: Re: perf problem with huge table From: Dave Crooke To: Jon Lewison Cc: rama , pgsql-performance@postgresql.org Content-Type: multipart/alternative; boundary=0016e6d785454035c6047f488d65 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.264 tagged_above=-10 required=5 tests=AWL=0.334, BAYES_00=-2.599, HTML_MESSAGE=0.001 X-Spam-Level: X-Archive-Number: 201002/172 X-Sequence-Number: 37593 --0016e6d785454035c6047f488d65 Content-Type: text/plain; charset=ISO-8859-1 Actually, in a way it does .... "No space left on device" or similar ;-) Cheers Dave P.S. for those not familiar with Oracle, ORA-01555 translates to "your query / transaction is kinda old and I've forgotten the data, so I'm just going to throw an error at you now". If you're reading, your SELECT randomly fails, if you're writing it forces a rollback of your transaction. On Wed, Feb 10, 2010 at 6:09 PM, Jon Lewison wrote: > > Speaking of rollback segments I'm assuming that since all storage for > non-visible row versions is in the main table that PostgreSQL has no > equivalent for an ORA-01555. > > - Jon > > --0016e6d785454035c6047f488d65 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Actually, in a way it does .... "No space left on device" or simi= lar ;-)

Cheers
Dave

P.S. for those not familiar with Oracl= e, ORA-01555 translates to "your query / transaction is kinda old and = I've forgotten the data, so I'm just going to throw an error at you= now". If you're reading, your SELECT randomly fails, if you'r= e writing it forces a rollback of your transaction.

On Wed, Feb 10, 2010 at 6:09 PM, Jon Lewison= <jlewison1@gma= il.com> wrote:

Speaking of rollback segments I'm assuming that since all storage f= or non-visible row versions is in the main table that PostgreSQL has no equ= ivalent for an ORA-01555.

- Jon


--0016e6d785454035c6047f488d65--