pgsql: On second thought, explain why date_trunc("week") on interval va

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: On second thought, explain why date_trunc("week") on interval va
Date: 2012-08-15 20:48:17
Message-ID: E1T1kVl-0006cD-GG@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On second thought, explain why date_trunc("week") on interval values is
not supported in the error message, rather than the docs.

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/083b9133aa0e5e91d74ba46b530a74989223324d

Modified Files
--------------
doc/src/sgml/func.sgml | 5 -----
src/backend/utils/adt/timestamp.c | 15 +++++++++++----
2 files changed, 11 insertions(+), 9 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Bruce Momjian 2012-08-15 22:30:40 Re: [COMMITTERS] pgsql: Clean up the #include mess a little.
Previous Message Bruce Momjian 2012-08-15 20:04:10 pgsql: Document why you can't use date_trunc("week") on intervals.