Re: perf problem with huge table

From: Dave Crooke <dcrooke(at)gmail(dot)com>
To: Jon Lewison <jlewison1(at)gmail(dot)com>
Cc: rama <rama(dot)rama(at)tiscali(dot)it>, pgsql-performance(at)postgresql(dot)org
Subject: Re: perf problem with huge table
Date: 2010-02-11 00:51:30
Message-ID: ca24673e1002101651o4f522489sce83b0c9b93281b0@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

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 <jlewison1(at)gmail(dot)com> 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
>
>

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Greg Smith 2010-02-11 01:42:13 Re: perf problem with huge table
Previous Message Jon Lewison 2010-02-11 00:09:17 Re: perf problem with huge table