The expected behavior was not obvious to me. "By default, there is no
explicit bound on precision" sounds more like "unlimited variable length",
as on the 'text' character type.
"By default, the bound on precision is 6 (that is, microsecond precision)"
conveys that 'timestamp with timezone' means
Kirk Parker writes:
> On Fri, Oct 13, 2023 at 7:32 AM David G. Johnston <
> david.g.johns...@gmail.com> wrote:
>> That is precisely what a no default with maximum of six means. If we say
>> the default is six that would imply storage of less precise values pads
>> significant zeros until there ar
Hi,
sorry it took me some time to reply. Yes, the patch is perfect if this is
indeed the behavior.
cheers
Daniel
Le jeu. 5 oct. 2023 à 02:50, Laurenz Albe a
écrit :
> On Wed, 2023-10-04 at 20:12 -0400, Daniel Fredouille wrote:
> > unnest ( anymultirange ) → setof anyrange
> > Expands a multira
On Fri, Oct 13, 2023 at 7:32 AM David G. Johnston <
david.g.johns...@gmail.com> wrote:
> On Friday, October 13, 2023, PG Doc comments form
> wrote:
>
>> both of them round any precision
>> beyond microseconds, and neither returns timestamps with greater precision
>> than the value that was insert
On Friday, October 13, 2023, PG Doc comments form
wrote:
> both of them round any precision
> beyond microseconds, and neither returns timestamps with greater precision
> than the value that was inserted.
>
That is precisely what a no default with maximum of six means. If we say
the default is
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/16/datatype-datetime.html
Description:
https://www.postgresql.org/docs/current/datatype-datetime.html says:
> time, timestamp, and interval accept an optional precision value p which
specifi
