|
1 | 1 | <!--
|
2 |
| -$PostgreSQL: pgsql/doc/src/sgml/ref/psql-ref.sgml,v 1.166 2006/07/27 19:52:04 tgl Exp $ |
| 2 | +$PostgreSQL: pgsql/doc/src/sgml/ref/psql-ref.sgml,v 1.167 2006/08/29 22:25:04 tgl Exp $ |
3 | 3 | PostgreSQL documentation
|
4 | 4 | -->
|
5 | 5 |
|
@@ -2007,6 +2007,33 @@ bar
|
2007 | 2007 | </listitem>
|
2008 | 2008 | </varlistentry>
|
2009 | 2009 |
|
| 2010 | + <varlistentry> |
| 2011 | + <term><varname>FETCH_COUNT</varname></term> |
| 2012 | + <listitem> |
| 2013 | + <para> |
| 2014 | + If this variable is set to an integer value > 0, |
| 2015 | + the results of <command>SELECT</command> queries are fetched |
| 2016 | + and displayed in groups of that many rows, rather than the |
| 2017 | + default behavior of collecting the entire result set before |
| 2018 | + display. Therefore only a |
| 2019 | + limited amount of memory is used, regardless of the size of |
| 2020 | + the result set. Settings of 100 to 1000 are commonly used |
| 2021 | + when enabling this feature. |
| 2022 | + Keep in mind that when using this feature, a query may |
| 2023 | + fail after having already displayed some rows. |
| 2024 | + </para> |
| 2025 | + <tip> |
| 2026 | + <para> |
| 2027 | + Although you can use any output format with this feature, |
| 2028 | + the default <literal>aligned</> format tends to look bad |
| 2029 | + because each group of <varname>FETCH_COUNT</varname> rows |
| 2030 | + will be formatted separately, leading to varying column |
| 2031 | + widths across the row groups. The other output formats work better. |
| 2032 | + </para> |
| 2033 | + </tip> |
| 2034 | + </listitem> |
| 2035 | + </varlistentry> |
| 2036 | + |
2010 | 2037 | <varlistentry>
|
2011 | 2038 | <term><varname>HISTCONTROL</varname></term>
|
2012 | 2039 | <listitem>
|
|
0 commit comments