Re: list of flags that pg_settings_get_flags reports

On Thu, Jul 21, 2022 at 12:19:59PM +0900, Fujii Masao wrote: > On 2022/07/20 16:26, Michael Paquier wrote: > > On Wed, Jul 20, 2022 at 01:51:36PM +0900, Fujii Masao wrote: > > > Attached is the updated version of the patch. It separates the list > > > for GUC flags from the table entry for pg_setti

Re: Unclear text at https://www.postgresql.org/docs/14/when-can-parallel-query-be-used.html

On Tue, Aug 09, 2022 at 09:05:51AM +, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/14/when-can-parallel-query-be-used.html > Description: > > "In addition, the system must not be running in single-u

Re: CREATE STATISTICS and partitoins/inheritance

On Wed, Aug 31, 2022 at 11:15:41PM -0400, Bruce Momjian wrote: > On Wed, Aug 17, 2022 at 03:30:11PM -0400, Bruce Momjian wrote: > > In looking at CREATE STATISTICS, I was confused how inheritance and > > partisions were handled, so I confirmed with Tomas that the ANALYZE > > manual page accurately

Re: systemd service start - disable timeout with "infinity"

On Sun, Mar 20, 2022 at 12:11:19PM -0400, Tom Lane wrote: > PG Doc comments form writes: > > In the service start section of the documentation, it is stated that using a > > value of zero for TimeoutSec disables the systemd timeout. This is not > > accurate and according to the documentation of sy

bad style for SECURITY DEFINER

The title of this section looks poor in the first two web browsers I tried. https://www.postgresql.org/docs/current/sql-createfunction.html#id-1.9.3.67.10.2 | Writing SECURITY DEFINER Functions Safely It looks like it may be the only tag within a . The PDF looks fine. -- Justin

Re: Add A Glossary

On Tue, Jun 16, 2020 at 08:09:26PM -0400, Alvaro Herrera wrote: > diff --git a/doc/src/sgml/glossary.sgml b/doc/src/sgml/glossary.sgml > index 25b03f3b37..e29b55e5ac 100644 > --- a/doc/src/sgml/glossary.sgml > +++ b/doc/src/sgml/glossary.sgml > @@ -395,15 +395,15 @@ > > The base directo

Re: Correction For PostgreSQL Manual

On Tue, Nov 05, 2019 at 08:54:46PM -0500, Bruce Momjian wrote: > On Fri, Oct 25, 2019 at 09:56:47PM +, PG Doc comments form wrote: > > The following documentation comment has been logged on the website: > > > > Page: https://www.postgresql.org/docs/12/bgworker.html > > Description: > > > > Th

link to Slow_Query_Questions from wiki/Main Page

Hi, I'm suggesting to link to: https://wiki.postgresql.org/wiki/Slow_Query_Questions >From either: https://wiki.postgresql.org/wiki/Main%20Page or: https://wiki.postgresql.org/wiki/Performance_Optimization I know it's a wiki, but it looks like I'm not allowed to edit the 'Main' page, so I'm aski

remove duplicated words in comments .. across lines

Inspired by David's patch [0], find attached fixing words duplicated, across line boundaries. I should probably just call the algorithm proprietary, but if you really wanted to know, I've suffered again through sed's black/slashes. time find . -name '*.c' -o -name '*.h' |xargs sed -srn '/\/\*/!d

Re: typo in parallel safety doc

On Fri, Aug 17, 2018 at 11:39:27AM +1200, Thomas Munro wrote: > On Fri, Aug 17, 2018 at 7:54 AM, Justin Pryzby wrote: > > https://www.postgresql.org/docs/10/static/parallel-safety.html > > |Even for simple functions where it conceivably be done, we do not try, > > since th

typo in parallel safety doc

https://www.postgresql.org/docs/10/static/parallel-safety.html |Even for simple functions where it conceivably be done, we do not try, since this would be expensive and error-prone. should say: "where it COULD conceivably"