diff options
| author | Bruce Momjian | 2011-06-09 18:32:50 +0000 |
|---|---|---|
| committer | Bruce Momjian | 2011-06-09 18:32:50 +0000 |
| commit | 6560407c7db2c7e32926a46f5fb52175ac10d9e5 (patch) | |
| tree | 9641e538893819410634624a8e0cb86a13d857a6 /src/timezone | |
| parent | adf43b2b36ca3d7f988933990051c74a4bd0d6f8 (diff) | |
Pgindent run before 9.1 beta2.
Diffstat (limited to 'src/timezone')
| -rw-r--r-- | src/timezone/pgtz.c | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/src/timezone/pgtz.c b/src/timezone/pgtz.c index 622cf94c5ad..ce6e7d1add9 100644 --- a/src/timezone/pgtz.c +++ b/src/timezone/pgtz.c @@ -1480,9 +1480,9 @@ pg_timezone_initialize(void) * postgresql.conf, this code will not do what you might expect, namely * call select_default_timezone() and install that value as the setting. * Rather, the previously active setting --- typically the one from - * postgresql.conf --- will be reinstalled, relabeled as PGC_S_ENV_VAR. - * If we did try to install the "correct" default value, the effect would - * be that each postmaster child would independently run an extremely + * postgresql.conf --- will be reinstalled, relabeled as PGC_S_ENV_VAR. If + * we did try to install the "correct" default value, the effect would be + * that each postmaster child would independently run an extremely * expensive search of the timezone database, bringing the database to its * knees for possibly multiple seconds. This is so unpleasant, and could * so easily be triggered quite unintentionally, that it seems better to |