On Tue, Jan 16, 2007 at 12:06:38 -0600,
Bruno Wolff III <[EMAIL PROTECTED]> 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.
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
