pgsql: Fix to_char(), to_date(), and to_timestamp() to handle negative/ - Mailing list pgsql-committers

From Bruce Momjian
Subject pgsql: Fix to_char(), to_date(), and to_timestamp() to handle negative/
Date
Msg-id E1SyngG-00028Q-IX@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Fix to_char(), to_date(), and to_timestamp() to handle negative/BC
century specifications just like positive/AD centuries.  Previously the
behavior was either wrong or inconsistent with positive/AD handling.

Centuries without years now always assume the first year of the century,
which is now documented.

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/ac78c4178bec7b252d22a39515ad6efd6c1a7d7e

Modified Files
--------------
doc/src/sgml/func.sgml                    |    4 ++-
src/backend/utils/adt/formatting.c        |   49 +++++++++++++++++++----------
src/test/regress/expected/timestamp.out   |    4 +-
src/test/regress/expected/timestamptz.out |    4 +-
4 files changed, 39 insertions(+), 22 deletions(-)


pgsql-committers by date:

Previous
From: Fujii Masao
Date:
Subject: Re: pgsql: fsync backup_label after pg_start_backup()
Next
From: fxjr@pgfoundry.org (User Fxjr)
Date:
Subject: npgsql - Npgsql2: [#1011215] AddString in NpgsqlCopySerializer.cs