Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1ihGby-00032b-J6 for pgsql-bugs@arkaria.postgresql.org; Tue, 17 Dec 2019 17:26:18 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1ihGbw-00052t-O0 for pgsql-bugs@arkaria.postgresql.org; Tue, 17 Dec 2019 17:26:16 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1ihGbw-00052m-B0 for pgsql-bugs@lists.postgresql.org; Tue, 17 Dec 2019 17:26:16 +0000 Received: from mail-pj1-x1044.google.com ([2607:f8b0:4864:20::1044]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1ihGbt-00048J-JZ for pgsql-bugs@lists.postgresql.org; Tue, 17 Dec 2019 17:26:15 +0000 Received: by mail-pj1-x1044.google.com with SMTP id n59so155381pjb.1 for ; Tue, 17 Dec 2019 09:26:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:subject:message-id:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=XvC8YTBa+nVaiRqsigxWCySUwByC13DcAQOTdJrjmgE=; b=2DSmGZWicp/Fj6G3vi+63sYubKQbAS9zga5FtZXrea40PydWu9SKi9JKRyZpGo5Iiv ht5nGkDrxpXkgg/D8kkAv3vaFqEgmAchcR/m9UHhMLLnYOiRFkvnI194DC61aBRHUrfW e6AcVDHQGe+fG8zfyybs4MbN2/zceSKdt3gT/Xqk0aeehr8xeaj9xOFqwpqTro850FS8 A2QYQ7/9l9NTpMrfCe8KheAX7qFMXa6YvfNdYiW+FthIIyJsJvkuC8uX/nUS5qA5SfSy s4BYvqLIsgqUuP0pnnOsdVypGv6DzVD41fj0shQVAOsTJAgNK+ce+XTFeXJWmqtmq4gb TQuw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=XvC8YTBa+nVaiRqsigxWCySUwByC13DcAQOTdJrjmgE=; b=YBBMEmGlCBytaAjlASz5Rug0M1Zqj2zwfaj7xZkPGsV7LIkCQfupvLfr/YVBn+mqc3 MWK/OjmvTndgH/c38fzLIhDH0PnhjXlaO7E/BiMxOmtbFOXzF7T8mnpHi2voaMjSauqu LMySklMOvj+hye7QDkW3MUgvrUF9vIZ33914FCu72dz0U5+A3FHdEqCREkqi7yVoSbfO 2nSXGRkd7FqFIdYypJ+tpqJtsq6uuNpcZZZnC1PrstQEzSSyFBBGk+B7V2fqPgy49nuf RsfwRqPgxoWOTYAfP6GbRK2r51tSq03oeJ7GGBUrzdAGnsg+ANiGbgo5rsNI0Jegl7TT 2E9A== X-Gm-Message-State: APjAAAW8aHqGwUWQS4ug9SXfvL7ZrJMDJawiVnto+VvVvvRVhuKxKDZH TQxZtFPLrg6K5WvQMOQlNr4mp9e0LK8rkOvhCFUNMaCfPrs2LKxZcYJmx5FUcfMhLvx6yzLxH5a 5M3Yym+rNC9huh9jtKhlc8SyrQuwKkN3eW6V0DFxjnF/Sf3EMQrriCw2iwhWOhy9WXkfyI3b5y+ YuaOqpxKF0zQOh X-Google-Smtp-Source: APXvYqwRsOfSdxELVBZii+VtP8CXh0Qf7BxUSo2QkGinWFK6rAArd0e+Axll9RyvMkiMXVbEMC3Qig== X-Received: by 2002:a17:902:ab86:: with SMTP id f6mr22861352plr.51.1576603571265; Tue, 17 Dec 2019 09:26:11 -0800 (PST) Received: from nimloth.alvh.no-ip.org ([190.121.29.3]) by smtp.gmail.com with ESMTPSA id c10sm28763924pfo.135.2019.12.17.09.26.09 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 17 Dec 2019 09:26:10 -0800 (PST) Received: by nimloth.alvh.no-ip.org (Postfix, from userid 1000) id 158273008FE; Tue, 17 Dec 2019 14:26:07 -0300 (-03) Date: Tue, 17 Dec 2019 14:26:07 -0300 From: Alvaro Herrera To: folarte@peoplecall.com, pgsql-bugs@lists.postgresql.org Subject: Re: BUG #16169: Default time output for 24:00 is 00:00 Message-ID: <20191217172607.GA10657@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <16169-db6039a4786ae5d7@postgresql.org> User-Agent: Mutt/1.10.1 (2018-07-13) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2019-Dec-17, PG Bug reporting form wrote: > The output correctly follows what the manual says ( > https://www.postgresql.org/docs/12/datatype-datetime.html ). Although the > doc is correct, I have not been able to find any explicit mention of this > behaviour. An explicit mention may be useful to avoid confusion, as one > normally expects to be able to reconstruct inserted data from select results > ( changing behaviour may hurt existing dependencies on current one ), and > 2400 may be a common value when using time fields for things like "opening > hours 16:00 - 24:00". Do you have a concrete proposal? I think 8.5.1.2 could have a new para saying "note that 24:00 is displayed as 00:00 because it really is the start of the next day, and there's no way to distinguish that from 00:00 of the current day." Or maybe it should just state that using a time column without an accompanying date column is a lost cause. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services