Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: SQL_CALC_FOUND_ROWS equivalent in PostgreSQL
- From: Michael Fuhr <mike(at)fuhr(dot)org>
- To: Oliver Elphick <olly(at)lfix(dot)co(dot)uk>
- Cc: "Matt Arnilo S. Baluyos (Mailing Lists)" <matt(dot)baluyos(dot)lists(at)gmail(dot)com>, pgsql-novice(at)postgresql(dot)org
- Subject: Re: SQL_CALC_FOUND_ROWS equivalent in PostgreSQL
- Date: Tue, 31 Jul 2007 08:32:16 -0600
- Message-id: <20070731143216.GA28226@winnie.fuhr.org> <text/plain>
On Tue, Jul 31, 2007 at 07:24:34AM +0100, Oliver Elphick wrote: > BEGIN; > SELECT * FROM mytable OFFSET X LIMIT Y; > SELECT COUNT(*) AS total FROM mytable; > END; > > (To ensure consistent results, both queries should be done in a single > transaction.) To ensure consistent results the transaction should be SERIALIZABLE. With the default of READ COMMITTED changes between the two selects would be visible to the second select. -- Michael Fuhr
- References:
- SQL_CALC_FOUND_ROWS equivalent in PostgreSQL
- From: Matt Arnilo S. Baluyos (Mailing Lists)
- Re: SQL_CALC_FOUND_ROWS equivalent in PostgreSQL
- From: Oliver Elphick
- SQL_CALC_FOUND_ROWS equivalent in PostgreSQL
- Prev by Date: Re: tsearch2.sql and different versions of PostgreSQL
- Previous by thread: Re: SQL_CALC_FOUND_ROWS equivalent in PostgreSQL
- Next by thread: alter table table add column
- Indexes: