On Wed, 2023-11-15 at 17:38 +, PG Doc comments form wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/16/sql-notify.html
> Description:
>
> It would be good to add to the notes section that use of NOTIFY especially
> within
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/16/sql-notify.html
Description:
It would be good to add to the notes section that use of NOTIFY especially
within a TRIGGER requires an AccessExclusiveLock which may cause performance
issues.
Erik Wienhold writes:
> On 2023-11-15 12:53 +0100, Peter Eisentraut wrote:
>> I think we should reframe "ISO" to mean "ISO 9075" and remove all claims of
>> alignment with ISO 8601 and RFC 3339.
> Agree. So just list the example inputs without any reference to a
> particular standard, except for
On 2023-11-15 12:53 +0100, Peter Eisentraut wrote:
> On 15.11.23 09:37, Erik Wienhold wrote:
> > On 2023-11-15 08:16 +0100, Peter Eisentraut wrote:
> > > The SQL standard does not refer to ISO 8601 to define date formats, it has
> > > its own definitions. In fact, PostgreSQL implements more date f
On 15.11.23 09:37, Erik Wienhold wrote:
On 2023-11-15 08:16 +0100, Peter Eisentraut wrote:
The SQL standard does not refer to ISO 8601 to define date formats, it has
its own definitions. In fact, PostgreSQL implements more date formats than
the SQL standard requires.
Really? Then what does t
On 2023-11-15 08:16 +0100, Peter Eisentraut wrote:
> The SQL standard does not refer to ISO 8601 to define date formats, it has
> its own definitions. In fact, PostgreSQL implements more date formats than
> the SQL standard requires.
Really? Then what does the standard mean with section "Definit
