Re: 19.9. Secure TCP/IP Connections with SSL

On Wed, Oct 25, 2023 at 03:44:04PM +, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/16/ssl-tcp.html > Description: > > There is no mention of key lengths on the manual page about SSL/TLS > connection

Re: pg_isready --dbname option is broken. So it should not be in the manual

On Thursday, October 26, 2023, Daniel Gustafsson wrote: > > On 26 Oct 2023, at 14:20, David G. Johnston > wrote: > > > > On Thursday, October 26, 2023, PG Doc comments form < > nore...@postgresql.org > wrote: > > The following documentation comment has been logged

Re: pg_isready --dbname option is broken. So it should not be in the manual

> On 26 Oct 2023, at 14:20, David G. Johnston > wrote: > > On Thursday, October 26, 2023, PG Doc comments form > wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/16/app-pg-isready.html >

Re: pg_isready --dbname option is broken. So it should not be in the manual

On Thursday, October 26, 2023, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/16/app-pg-isready.html > Description: > > the --dbname option in pg_isready seems not to work propperly. the tool > returns 'o

pg_isready --dbname option is broken. So it should not be in the manual

The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/16/app-pg-isready.html Description: the --dbname option in pg_isready seems not to work propperly. the tool returns 'ok' as long as the cluster itselft is running, no matter how wrong the bdn

Re: Example 43.6. A PL/pgSQL Trigger Function for Maintaining a Summary Table

I believe that the attached patch should fix this problem. Please have a look. 26.10.2023 12:29, Daniel Gustafsson пишет: On 26 Oct 2023, at 09:33, Maxim Yablokov wrote: Example 43.6 on the pagehttps://www.postgresql.org/docs/16/plpgsql-trigger.html has two tables called main. But it seems t

Re: Example 43.6. A PL/pgSQL Trigger Function for Maintaining a Summary Table

Yeah, sure thing! Thanks! I'll send a patch soon. 26.10.2023 12:29, Daniel Gustafsson пишет: On 26 Oct 2023, at 09:33, Maxim Yablokov wrote: Example 43.6 on the pagehttps://www.postgresql.org/docs/16/plpgsql-trigger.html has two tables called main. But it seems that the table time_dimension i

Re: Example 43.6. A PL/pgSQL Trigger Function for Maintaining a Summary Table

> On 26 Oct 2023, at 09:33, Maxim Yablokov wrote: > Example 43.6 on the page > https://www.postgresql.org/docs/16/plpgsql-trigger.html has two tables called > main. But it seems that the table time_dimension is not used any further, > it's a bit strange for one of main tables of the example. A

19.9. Secure TCP/IP Connections with SSL

The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/16/ssl-tcp.html Description: There is no mention of key lengths on the manual page about SSL/TLS connections even though there are restrictions. It probably depends on the build which is why

Example 43.6. A PL/pgSQL Trigger Function for Maintaining a Summary Table

Hello! Example 43.6 on the page https://www.postgresql.org/docs/16/plpgsql-trigger.html has two tables called main. But it seems that the table *time_dimension* is not used any further, it's a bit strange for one of main tables of the example. Am I missing something, or should this example be