Re: Performance with very large tables - Mailing list pgsql-general

From Bruno Wolff III
Subject Re: Performance with very large tables
Date
Msg-id 20070116181158.GB15932@wolff.to
Whole thread Raw
In response to Re: Performance with very large tables  (Bruno Wolff III <bruno@wolff.to>)
List pgsql-general
On Tue, Jan 16, 2007 at 12:06:38 -0600,
  Bruno Wolff III <bruno@wolff.to> wrote:
>
> Depending on exactly what you want to happen, you may be able to continue
> where you left off using a condition on the primary key, using the last
> primary key value for a row that you have viewed, rather than OFFSET.
> This will still be fast and will not skip rows that are now visible to
> your transaction (or show duplicates when deleted rows are no longer visible
> to your transaction).

I should have mentioned that you also will need to use an ORDER BY clause
on the primary key when doing things this way.

pgsql-general by date:

Previous
From: "Lenorovitz, Joel"
Date:
Subject: Temp Table Within PLPGSQL Function - Something Awry
Next
From: Martijn van Oosterhout
Date:
Subject: Re: Temp Table Within PLPGSQL Function - Something Awry