Oh, thank you very much for the clarification. Kind regards Peter
On Fri, Jul 18, 2025, 15:31 Laurenz Albe wrote:
> On Thu, 2025-07-17 at 12:59 +, PG Doc comments form wrote:
> > The last table of page
> https://www.postgresql.org/docs/current/ddl-priv.html
> > shows that column ' Access pri
On Thu, 2025-07-17 at 12:59 +, PG Doc comments form wrote:
> The last table of page https://www.postgresql.org/docs/current/ddl-priv.html
> shows that column ' Access privileges' can contain plus-signs at the end,
> but what these plus-signs mean does not seem to be explained anywhere.
That ha
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/17/ddl-priv.html
Description:
The last table of page https://www.postgresql.org/docs/current/ddl-priv.html
shows that column ' Access privileges' can contain plus-signs at the end,
but what t
Ok. Yes, changing the existing behaviour could lead to back compatibility issues. But have you found the functionality to "make an option unrecognizable again" useful? In theory, would it be appropriate to have eg. "UNSET" to perform that?
Кому: KES (kes-...@
I never saw such examples before and never thought that I can pass two composite types into ORDER BY clause. Because this section is about composite types, I found it could be useful to highlight that possibility. Otherwise it is too implicit. at least for not so experienced users like me. ---
On Fri, Jul 18, 2025 at 12:33 PM Fujii Masao
wrote:
>
>
>
> On 2025/07/18 11:35, Shinya Kato wrote:
> > On Thu, Jul 10, 2025 at 4:48 PM Fujii Masao
> > wrote:
> >>
> >> Hi,
> >>
> >> pg_recvlogical continuously writes to the file specified with the --file
> >> option,
> >> which means the outpu
