On Mon, 2023-11-13 at 16:08 -0500, Bruce Momjian wrote:
> Backpatched to PG 16.
Thanks!
Yours,
Laurenz Albe
On Thu, Nov 2, 2023 at 06:22:59PM -0400, Bruce Momjian wrote:
> On Thu, Nov 2, 2023 at 03:42:53PM +0100, Laurenz Albe wrote:
> > On Thu, 2023-11-02 at 10:14 -0400, Bruce Momjian wrote:
> > > Better, though "Is the range's upper bound unbounded?" makes me cringe.
> > >
> > > Oh, yeah, totally cri
On Thu, Nov 2, 2023 at 11:08:53AM -0400, Bruce Momjian wrote:
> On Thu, Nov 2, 2023 at 09:58:54AM -0400, Tom Lane wrote:
> > Bruce Momjian writes:
> > > I found a cleaner improvement, attached.
> >
> > OK by me. Maybe that doesn't make the point strongly enough,
> > but we can hope it's enough
Erik Wienhold writes:
> On 2023-11-13 15:24 +0100, Erik Wienhold wrote:
>> I also noticed that when people say "ISO 8601" they usually mean RFC
>> 3389 or some subset of ISO 8601.
> Forgot this fine visualization of the differences:
> https://ijmacd.github.io/rfc3339-iso8601/
I'm inclined not to
On 2023-11-13 15:24 +0100, Erik Wienhold wrote:
> I also noticed that when people say "ISO 8601" they usually mean RFC
> 3389 or some subset of ISO 8601.
Forgot this fine visualization of the differences:
https://ijmacd.github.io/rfc3339-iso8601/
--
Erik
On 2023-11-13 12:27 +0100, Roman Frołow wrote:
> It seems I was wrong.
> Now T is mandatory in ISO8601 and from RFC3339 it seems this requirement is
> relaxed.
Right. RFC 3339 is from 2002 and it references ISO 8601:1988 where T
was optional. (Until today I didn't even know about the 2019 editio
> On 13 Nov 2023, at 12:20, Alvaro Herrera wrote:
>
> On 2023-Nov-13, Daniel Gustafsson wrote:
>
>> That's a fair point. It's sort of hard to refer back from the acronym list
>> though since we don't have a single Access Method section but instead one for
>> Indexes and one for Relations. In
It seems I was wrong.
Now T is mandatory in ISO8601 and from RFC3339 it seems this requirement is
relaxed.
-
https://stackoverflow.com/questions/9531524/in-an-iso-8601-date-is-the-t-character-mandatory#comment89287877_34006233
-
https://en.m.wikipedia.org/wiki/ISO_8601#Combined_date_and_time_repre
So what should be changed?
postgresql docs say that it is consistent with rfc3339 using space.
Also look at this:
> In addition, an uppercase "T" character MUST be used to separate date and
time
https://validator.w3.org/feed/docs/error/InvalidRFC3339Date.html
I would say that postgresql is not
> On 10 Nov 2023, at 22:00, PG Doc comments form wrote:
>
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/16/sql-select.html
> Description:
>
> Hi,
>
> To be consistent, the "with" example should end in a ";".
>
> WITH t AS (
>
On 2023-Nov-13, Daniel Gustafsson wrote:
> That's a fair point. It's sort of hard to refer back from the acronym list
> though since we don't have a single Access Method section but instead one for
> Indexes and one for Relations. In the attached diff I propose that we add a
> glossary entry for
> On 12 Nov 2023, at 00:08, PG Doc comments form wrote:
>
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/16/acronyms.html
> Description:
>
> while reading the progres codebase, i could find you're using the acronym
> "AM" which de
On 2023-11-11 23:45 +0100, PG Doc comments form wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/16/git.html
> Description:
>
> >ISO 8601 specifies the use of uppercase letter T to separate the date and
> time. PostgreSQL accep
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/16/git.html
Description:
>ISO 8601 specifies the use of uppercase letter T to separate the date and
time. PostgreSQL accepts that format on input, but on output it uses a space
rather than T,
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/16/sql-select.html
Description:
Hi,
To be consistent, the "with" example should end in a ";".
WITH t AS (
SELECT random() as x FROM generate_series(1, 3)
)
SELECT * FROM t
UNION ALL
S
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/16/acronyms.html
Description:
while reading the progres codebase, i could find you're using the acronym
"AM" which denotes "Access Method". it's be nice to add it to the list of
acronyms
16 matches
Mail list logo
