|
1 | | -<!-- $PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.209 2009/02/22 23:50:30 tgl Exp $ --> |
| 1 | +<!-- $PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.210 2009/02/24 12:09:08 petere Exp $ --> |
2 | 2 |
|
3 | 3 | <chapter Id="runtime-config"> |
4 | 4 | <title>Server Configuration</title> |
@@ -2398,16 +2398,20 @@ local0.* /var/log/postgresql |
2398 | 2398 | so <literal>%</literal>-escapes can be used to specify time-varying |
2399 | 2399 | file names. (Note that if there are |
2400 | 2400 | any time-zone-dependent <literal>%</literal>-escapes, the computation |
2401 | | - is done in the zone specified by <xref linkend="guc-log-timezone">.) |
2402 | | - If no <literal>%</literal>-escapes are present, |
2403 | | - <productname>PostgreSQL</productname> will append the epoch of the new |
2404 | | - log file's creation time. For example, if |
2405 | | - <varname>log_filename</varname> were <literal>server_log</literal>, |
2406 | | - then the chosen file name would be <literal>server_log.1093827753</> |
2407 | | - for a log starting at Sun Aug 29 19:02:33 2004 MST. |
| 2401 | + is done in the zone specified |
| 2402 | + by <xref linkend="guc-log-timezone">.) |
2408 | 2403 | Note that the system's <systemitem>strftime</systemitem> is not used |
2409 | 2404 | directly, so platform-specific (nonstandard) extensions do not work. |
2410 | 2405 | </para> |
| 2406 | + <para> |
| 2407 | + If you specify a file name without escapes, you should plan to |
| 2408 | + use a log rotation utility to avoid eventually filling the |
| 2409 | + entire disk. In releases prior to 8.4, if |
| 2410 | + no <literal>%</literal> escapes were |
| 2411 | + present, <productname>PostgreSQL</productname> would append |
| 2412 | + the epoch of the new log file's creation time, but this is no |
| 2413 | + longer the case. |
| 2414 | + </para> |
2411 | 2415 | <para> |
2412 | 2416 | If CSV-format output is enabled in <varname>log_destination</>, |
2413 | 2417 | <literal>.csv</> will be appended to the timestamped |
|
0 commit comments