|
1 | 1 | <!-- |
2 | | -$PostgreSQL: pgsql/doc/src/sgml/func.sgml,v 1.274 2005/07/3014:52:04 momjian Exp $ |
| 2 | +$PostgreSQL: pgsql/doc/src/sgml/func.sgml,v 1.275 2005/07/3022:53:15 tgl Exp $ |
3 | 3 | PostgreSQL documentation |
4 | 4 | --> |
5 | 5 |
|
@@ -4903,24 +4903,6 @@ SELECT SUBSTRING('XY1234Z', 'Y*?([0-9]{1,3})'); |
4903 | 4903 | such pair. |
4904 | 4904 | </para> |
4905 | 4905 |
|
4906 | | - <para> |
4907 | | - When adding an <type>interval</type> value to (or subtracting an |
4908 | | - <type>interval</type> value from) a <type>timestamp with time zone</type> |
4909 | | - value, the days component advances (or decrements) the date of the |
4910 | | - <type>timestamp with time zone<type> by the indicated number of days. |
4911 | | - Across daylight saving time changes (with the session tiem zone set to a |
4912 | | - time zone that recognizes DST), this means <literal>interval '1 day'</literal> |
4913 | | - does not necessarily equal <literal>interval '24 hours'</literal>. |
4914 | | - For example, with the session time zone set to <literal>CST7CDT</literal> |
4915 | | - <literal>timestamp with time zone '2005-04-02 12:00-07' + interval '1 day' </literal> |
4916 | | - will produce <literal>timestamp with time zone '2005-04-03 12:00-06'</literal>, |
4917 | | - while adding <literal>interval '24 hours'</literal> to the same initial |
4918 | | - <type>timestamp with time zone</type> produces |
4919 | | - <literal>timestamp with time zone '2005-04-03 13:00-06'</literal>, as there is |
4920 | | - a change in daylight saving time at <literal>2005-04-03 02:00</literal> in time zone |
4921 | | - <literal>CST7CDT</literal>. |
4922 | | - </para> |
4923 | | - |
4924 | 4906 | <table id="operators-datetime-table"> |
4925 | 4907 | <title>Date/Time Operators</title> |
4926 | 4908 |
|
@@ -5241,6 +5223,24 @@ SELECT (DATE '2001-02-16', INTERVAL '100 days') OVERLAPS |
5241 | 5223 | <lineannotation>Result: </lineannotation><computeroutput>false</computeroutput> |
5242 | 5224 | </screen> |
5243 | 5225 |
|
| 5226 | + <para> |
| 5227 | + When adding an <type>interval</type> value to (or subtracting an |
| 5228 | + <type>interval</type> value from) a <type>timestamp with time zone</type> |
| 5229 | + value, the days component advances (or decrements) the date of the |
| 5230 | + <type>timestamp with time zone</type> by the indicated number of days. |
| 5231 | + Across daylight saving time changes (with the session time zone set to a |
| 5232 | + time zone that recognizes DST), this means <literal>interval '1 day'</literal> |
| 5233 | + does not necessarily equal <literal>interval '24 hours'</literal>. |
| 5234 | + For example, with the session time zone set to <literal>CST7CDT</literal>, |
| 5235 | + <literal>timestamp with time zone '2005-04-02 12:00-07' + interval '1 day' </literal> |
| 5236 | + will produce <literal>timestamp with time zone '2005-04-03 12:00-06'</literal>, |
| 5237 | + while adding <literal>interval '24 hours'</literal> to the same initial |
| 5238 | + <type>timestamp with time zone</type> produces |
| 5239 | + <literal>timestamp with time zone '2005-04-03 13:00-06'</literal>, as there is |
| 5240 | + a change in daylight saving time at <literal>2005-04-03 02:00</literal> in time zone |
| 5241 | + <literal>CST7CDT</literal>. |
| 5242 | + </para> |
| 5243 | + |
5244 | 5244 | <sect2 id="functions-datetime-extract"> |
5245 | 5245 | <title><function>EXTRACT</function>, <function>date_part</function></title> |
5246 | 5246 |
|
@@ -9275,17 +9275,17 @@ SELECT set_config('log_statement_stats', 'off', false); |
9275 | 9275 | <primary>pg_relation_size</primary> |
9276 | 9276 | </indexterm> |
9277 | 9277 | <para> |
9278 | | -<function>pg_relation_size</> accepts the oid or name of a table, index or |
9279 | | -toast table, and returns the size in bytes. |
| 9278 | +<function>pg_relation_size</> accepts the oid or name of a table, index or |
| 9279 | +toast table, and returns the size in bytes. |
9280 | 9280 | </para> |
9281 | 9281 | <para> |
9282 | | -<function>pg_complete_relation_size</> accepts the oid or name of a table or |
9283 | | -toast table, and returns the size in bytes of the data and all associated |
| 9282 | +<function>pg_complete_relation_size</> accepts the oid or name of a table or |
| 9283 | +toast table, and returns the size in bytes of the data and all associated |
9284 | 9284 | indexes and toast tables. |
9285 | 9285 | </para> |
9286 | 9286 | <para> |
9287 | | -<function>pg_size_pretty</> can be used to format the size of the |
9288 | | -database objects in a human readable way, using kB, MB, GB or TB as appropriate. |
| 9287 | +<function>pg_size_pretty</> can be used to format the size of the |
| 9288 | +database objects in a human readable way, using kB, MB, GB or TB as appropriate. |
9289 | 9289 | </para> |
9290 | 9290 |
|
9291 | 9291 | </sect1> |
|