The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/15/logicaldecoding-synchronous.html
Description:
Very minor suggestion. Earlier on this page, commands are referred to that
can cause "a deadlock". Later on the page, it says "cause deadlock"
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/15/sql-comment.html
Description:
I've recently been converting some DML which was intended for BigQuery to
use PostgreSQL 14. Using a python client (using sqlalchemy and the
postgresql+psyco
On Fri, 21 Oct 2022 at 09:23, PG Doc comments form
wrote:
>
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/15/sql-comment.html
> Description:
>
> I've recently been converting some DML which was intended for BigQuery to
> use Postgre
Hi!
I have 2 small ideas to improve the usability of the PostgreSQL documentation.
I'm looking at v15 (1) mostly.
Idea 1:
Give the text width of the main content a max width.
Idea 2:
Each h3 and h4 element should be a link pointing to the nearest parent section
with an id. This makes deeplinki
Hi,
Thanks for the suggestions. Comments inline:
On 10/21/22 9:54 AM, Niels Bom wrote:
Hi!
I have 2 small ideas to improve the usability of the PostgreSQL documentation.
I'm looking at v15 (1) mostly.
Idea 1:
Give the text width of the main content a max width.
Why? Can you please provide
On Fri, Oct 21, 2022, at 17:42, Jonathan S. Katz wrote:
> Hi,
>
> Thanks for the suggestions. Comments inline:
>
> On 10/21/22 9:54 AM, Niels Bom wrote:
>> Hi!
>>
>> I have 2 small ideas to improve the usability of the PostgreSQL
>> documentation. I'm looking at v15 (1) mostly.
>>
>> Idea 1:
>>
