|
1 | 1 | <!-- |
2 | | -$PostgreSQL: pgsql/doc/src/sgml/ref/select.sgml,v 1.100 2007/05/15 19:13:55 neilc Exp $ |
| 2 | +$PostgreSQL: pgsql/doc/src/sgml/ref/select.sgml,v 1.101 2007/06/08 20:26:18 tgl Exp $ |
3 | 3 | PostgreSQL documentation |
4 | 4 | --> |
5 | 5 |
|
@@ -810,6 +810,14 @@ OFFSET <replaceable class="parameter">start</replaceable> |
810 | 810 | to deliver the results of a query in any particular order unless |
811 | 811 | <literal>ORDER BY</> is used to constrain the order. |
812 | 812 | </para> |
| 813 | + |
| 814 | + <para> |
| 815 | + It is even possible for repeated executions of the same <literal>LIMIT</> |
| 816 | + query to return different subsets of the rows of a table, if there |
| 817 | + is not an <literal>ORDER BY</> to enforce selection of a deterministic |
| 818 | + subset. Again, this is not a bug; determinism of the results is |
| 819 | + simply not guaranteed in such a case. |
| 820 | + </para> |
813 | 821 | </refsect2> |
814 | 822 |
|
815 | 823 | <refsect2 id="SQL-FOR-UPDATE-SHARE"> |
|