[DOCS] [9.3] Should we mention "set_config(...)" in 18.1.3 in Server Configuration?

Section 18.1.3 is named "18.1.3. Other Ways to Set Parameters" yet does not reference the ability to use "set_config(...)" to make changes to configuration parameters. Something like (as a final sentence): An alternative to the SQL "SET" command is to use the [link]set_config[link] function. Al

[DOCS] Some qualms with the current description of RegExp s,n,w modes.

The current documentation for "n" and "w" are as follows: [s] If partial newline-sensitive matching is specified, this affects . and bracket expressions as with newline-sensitive matching, but not ^ and $. [w] If inverse partial newline-sensitive matching is specified, this affects ^ and $ as wit

Re: [DOCS] disabling log_rotation_age feature.

Tomonari Katsumata-2 wrote > Hi, > > I'm reading about log_rotation_age. > And I noticed that the setting for disabling the feature is not clear. > > > The document tells us to set it to ZERO if we want to disable the feature. > However, the feature would be disabled if we set it less than one m

Re: [DOCS] disabling log_rotation_age feature.

David G Johnston wrote > > Tomonari Katsumata-2 wrote >> Hi, >> >> I'm reading about log_rotation_age. >> And I noticed that the setting for disabling the feature is not clear. >> >> >> The document tells us to set it to ZERO if we want to

Re: [DOCS] disabling log_rotation_age feature.

On Thu, Jun 12, 2014 at 10:42 AM, Tom Lane-2 [via PostgreSQL] < ml-node+s1045698n5807014...@n5.nabble.com> wrote: > Fujii Masao <[hidden email] > > writes: > > On Thu, Jun 12, 2014 at 1:43 PM, Tomonari Katsumata > > <[hidden email]

Re: [DOCS] [PATCH] Various documentation typo/grammar fixes

Tom Lane-2 wrote > Kevin Grittner < > kgrittn@ > > writes: >> Patch 1 pushed, with each fix back-patched as far as the error >> exists in supported releases.  I held off on patch 2 -- partly >> because I spotted at least one case where things weren't quite >> right, partly because there's so much

Re: [DOCS] NULL as a (pseudo-)value not described?

johnlumby wrote > As far as I can tell,   > the un-value NULL is not described anywhere in the doc > as being something that can be assigned to a column. > > E.g. : >    .  not listed as a constant  (well that's reasonable as it isn't) >     .  not listed as an expression  (is NULL an expression?

Re: [DOCS] The IYYY mess again

Tom Lane-2 wrote > In bug #12367 > http://www.postgresql.org/message-id/ > 20141229031218.8013.51171@.postgresql > > There is a warning against combining IYYY with MM/DD, but it's buried > in trivia far down the page. Can we move this warning/notice into code? Basically warn/disallow IYYY-MM-D

Re: [DOCS] Aggregate expression syntax

Tom Lane-2 wrote > Thom Brown < > thom@ > > writes: >> Looking at the syntax for aggregate expressions in the docs, it seems the >> first three forms could perhaps be merged since the ALL and DISTINCT >> keywords are effectively optional. > > Dunno, just seems harder to read to me... I'm genera

Re: [DOCS] how do I suggest a small docs change?

J Connolly wrote > Hi, just wondering how to suggest a small change to the docs. On a related > note, if the source was on github it would be easier for people like me to > suggest a change. Just post your thoughts to -docs. The harder part of doc changes is SGML, not the fact the Git repo is not

[DOCS] ROW or RANGE not optional in range specification

http://www.postgresql.org/docs/devel/static/sql-select.html Either I'm confused about the syntax description rules or the documentation for this aspect of window definitions is wrong. The expression: [ RANGE | ROWS ] BETWEEN frame_start AND frame_end means that the specification of range or ro

[DOCS] Add a new table for Transaction Isolation?

http://www.postgresql.org/docs/9.4/static/transaction-iso.html Table 13-1 shows the SQL standard isolation levels and what is and is not guaranteed. Then the text goes on to explain how our implementation differs from that table. Is there any opposition to actually adding a similar table, 13-2,

Re: [DOCS] Add a new table for Transaction Isolation?

On Wednesday, April 15, 2015, Bruce Momjian wrote: > On Mon, Apr 13, 2015 at 08:00:38PM -0700, David G. Johnston wrote: > > http://www.postgresql.org/docs/9.4/static/transaction-iso.html > > > > Table 13-1 shows the SQL standard isolation levels and what is and is not >

Re: [DOCS] Add a new table for Transaction Isolation?

ould think to go there for additional information. No like though - just a pointer to it or the Internet generally. It is not obvious to me what means...I suspect 1=yes... David J. On Wed, Apr 15, 2015 at 6:26 PM, David G. Johnston < david.g.johns...@gmail.com> wrote: > On Wednesday, Ap

Re: [DOCS] Add a new table for Transaction Isolation?

On Fri, Apr 24, 2015 at 9:57 AM, Peter Eisentraut wrote: > On 4/17/15 7:36 PM, David G. Johnston wrote: > > diff --git a/doc/src/sgml/mvcc.sgml b/doc/src/sgml/mvcc.sgml > > index f88b16e..5002138 100644 > > --- a/doc/src/sgml/mvcc.sgml > > +++ b/doc/src/sgml/mvcc

Re: [DOCS] Add a new table for Transaction Isolation?

On Sat, Apr 25, 2015 at 11:02 AM, Bruce Momjian wrote: > On Fri, Apr 24, 2015 at 08:40:40PM +, Kevin Grittner wrote: > > And, for reasons given above, I really question whether such a > > table doesn't do more harm than good. Even those citing the paper > > by Berenson, et al., often miss th

Re: [DOCS] Add a new table for Transaction Isolation?

On Saturday, April 25, 2015, Kevin Grittner wrote: > Bruce Momjian > wrote: > > On Sat, Apr 25, 2015 at 07:45:35PM +, Kevin Grittner wrote: > > >> We could perhaps have the column header say "Non-Serializable > >> Behavior" or some such; but I think we need to define whatever > >> term we use

Re: [DOCS] Add a new table for Transaction Isolation?

On Saturday, April 25, 2015, Bruce Momjian wrote: > On Sat, Apr 25, 2015 at 08:47:47PM +, Kevin Grittner wrote: > > Maybe something like "Prohibited", "Allowed but not Possible", and > > "Possible"? That would take a little explaining above, since our > > documentation's table would be devia

Re: [DOCS] Add a new table for Transaction Isolation?

On Saturday, April 25, 2015, David G. Johnston wrote: > On Saturday, April 25, 2015, Kevin Grittner > wrote: > >> Bruce Momjian wrote: >> > On Sat, Apr 25, 2015 at 07:45:35PM +, Kevin Grittner wrote: >> >> >> We could perhaps have the column heade

Re: [DOCS] "Alter system" command documentation

On Mon, Jun 15, 2015 at 4:58 PM, Euler Taveira wrote: > On 15-06-2015 13:32, Jeff Janes wrote: > > From http://www.postgresql.org/docs/current/static/sql-altersystem.html > > > > "Values set with ALTER SYSTEM will be effective after the next server > > configuration reload (SIGHUP or pg_ctl reloa

[DOCS] Omission of "(or C)" in psql's "pset title" header

http://www.postgresql.org/docs/devel/static/app-psql.html The other pset keywords with black-slash aliases include a "(or )" paren after the keyword. "title" does not (should be "C") David J.

[DOCS] Incomplete description in Create Operator (function arg order must match too)

http://www.postgresql.org/docs/devel/static/plpgsql-statements.html """ The function_name procedure must have been previously defined using CREATE FUNCTION and must be defined to accept the correct number of arguments (either one or two) of the indicated types. """ This should also include a comm

Re: [DOCS] Omission of "(or C)" in psql's "pset title" header

On Wed, Aug 26, 2015 at 10:02 PM, Bruce Momjian wrote: > On Wed, Jun 24, 2015 at 06:11:20PM -0400, David G. Johnston wrote: > > http://www.postgresql.org/docs/devel/static/app-psql.html > > > > The other pset keywords with black-slash aliases include a "(or > )

Re: [DOCS] Omission of "(or C)" in psql's "pset title" header

On Thu, Aug 27, 2015 at 11:13 AM, Bruce Momjian wrote: > On Wed, Aug 26, 2015 at 10:51:09PM -0400, David G. Johnston wrote: > > On Wed, Aug 26, 2015 at 10:02 PM, Bruce Momjian > wrote: > > > > On Wed, Jun 24, 2015 at 06:11:20PM -0400, David G. Johnst

Re: [DOCS] Omission of "(or C)" in psql's "pset title" header

On Thursday, August 27, 2015, Bruce Momjian wrote: > On Thu, Aug 27, 2015 at 11:50:53AM -0400, David G. Johnston wrote: > > ​Yes, I read that as "\pset tuples_only" and "\t" are alternate forms of > the > > same thing > > ​ and thought that "\pset

Re: [DOCS] Docs claim that "select myTable.*" wildcard won't let you assign column names

On Monday, September 21, 2015, Amir Rohan wrote: > > From http://www.postgresql.org/docs/9.4/static/sql-select.html (and > previous version too): > ##SELECT List > <...> > Instead of an expression, * can be written in the output list as a > shorthand for all the columns of the selected

Re: [DOCS] Docs claim that "select myTable.*" wildcard won't let you assign column names

ere feature a query example show the use of a > wildcard for columns > >> as well as allowing you to assign names to as many of the leading > columns as you wish: > >> > >> > >> WITH T0 as ( SELECT 1,2,3 ) > >> SELECT T0.* from T0 as T0(foo,bar) ;<

[DOCS] Annoying "split to array" function inconsistency...best way to fix?

Two functions exists that convert "text" to "text[]" regexp_string_to_array(text, text [,text]) : http://www.postgresql.org/docs/9.4/interactive/functions-string.html string_to_array(text, text [, text]) : http://www.postgresql.org/docs/9.4/interactive/functions-array.html Would it be hateful to

[DOCS] max_worker_processes default not documented

While this may be in the postgresql.conf it's absence in the docs is made noticeable by the fact both the immediately preceding and subsequent items in the 9.6 docs specify their default values. Furthermore, max_parallel_degree defaults to 2 but the workers come from the pool sized using max_worke

[DOCS] max_worker_processes default not documented

On Thursday, May 12, 2016, Peter Eisentraut < peter.eisentr...@2ndquadrant.com > wrote: > On 5/7/16 11:16 PM, David G. Johnston wrote: > >> While this may be in the postgresql.conf it's absence in the docs is made >> noticeable by the fact both the immediately precedi

[DOCS] Is this example regarding aggregates sourced by subquery correct?

http://www.postgresql.org/docs/9.5/static/functions-aggregate.html """ ...This ordering is unspecified by default, but can be controlled by writing an ORDER BY clause within the aggregate call, as shown in Section 4.2.7. Alternatively, supplying the input values from a sorted subquery will usually

Re: [DOCS] Is this example regarding aggregates sourced by subquery correct?

On Fri, May 20, 2016 at 5:07 PM, Tom Lane wrote: > "David G. Johnston" writes: > > http://www.postgresql.org/docs/9.5/static/functions-aggregate.html > > """ > > SELECT xmlagg(x) FROM (SELECT x FROM test ORDER BY y DESC) AS tab; > > But this s

Re: [DOCS] Is this example regarding aggregates sourced by subquery correct?

On Saturday, May 21, 2016, Tom Lane wrote: > "David G. Johnston" > writes: > > Based upon what you've said I would soften it a bit. Given my own > > experience I'd probably point out what is now obvious to me - that the > > allowance of the ORDER BY

[DOCS] Typo in Create Database Synopsis

The second closing bracket after "connlimit" should be moved after "istemplate ]" The IS_TEMPLATE option can be prefixed by "WITH" when used alone. i.e., create database newdb with is_template false; David J.

[DOCS] Clarification of "void" type

The section on pseudo-types names "void" and describes is thusly: """ Indicates that a function returns no value. """ This can be reasonably interpreted to mean: "Use this when you don't want the execution of a function to return a value." (i.e., the empty set) The following paragraph, suitably

Re: [DOCS] Undocumented behavior od DROP SCHEMA ... CASCADE

On Fri, Aug 12, 2016 at 8:54 AM, Vik Fearing wrote: > On 12/08/16 14:47, Peter Eisentraut wrote: > > On 8/5/16 6:48 AM, denisa.cirste...@asentinel.com wrote: > >> Page: https://www.postgresql.org/docs/9.5/static/sql-dropschema.html > >> Description: > >> > >> DROP SCHEMA ... CASCADE has a behavio

Re: [DOCS] Undocumented behavior od DROP SCHEMA ... CASCADE

On Fri, Aug 12, 2016 at 6:01 PM, Tom Lane wrote: > Alvaro Herrera writes: > > Tom Lane wrote: > >> There's plenty of discoverability already. The documentation suggests > >> > >> (If you want to check what DROP ... CASCADE will do, > >> run DROP without CASCADE and read the > >> DETAIL output.)

Re: [DOCS] Window function docs

On Thu, Apr 6, 2017 at 2:49 PM, Bruce Momjian wrote: > As part of writing a talk about window functions, I have done some > cleanups of the window function docs, attached, that I would like to > apply to head. +1 Overall. Some minor technical items noted below. The only conceptual item is whe

Re: [DOCS] Window function docs

On Thu, Apr 6, 2017 at 6:14 PM, Bruce Momjian wrote: > On Thu, Apr 6, 2017 at 03:53:24PM -0700, David G. Johnston wrote: > > > hypothetical-set aggregates as being distinct from ordered-set > aggregates yet > > the tables and the docs here do. > > Do you have

Re: [DOCS] default paramater is off

On Thu, May 11, 2017 at 12:55 AM, wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/9.5/static/runtime- > config-error-handling.html > Description: > > 18.14. Error Handling > exit_on_error (boolean) > If true, any error will te

Re: [DOCS] typo

On Wed, May 17, 2017 at 6:13 AM, wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/9.6/static/ddl-constraints.html > Description: > > https://www.postgresql.org/docs/9.6/static/ddl-constraints.html#DDL- > CONSTRAINTS-FK > > "If

Re: [DOCS] Incorrect commands in manual for 9.6

On Wednesday, May 24, 2017, wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/9.6/static/tutorial-createdb.html > Description: > > In the Postgresql Documentation manual for 9.6.3. I am using windows system > and when i execute

Re: [DOCS] nothing ever works

>>> 2017-06-21 10:39 GMT+02:00 : >>> >>> Your documentation although it seems straight forward actually never >>> works. Most of it is not written as self-contained examples so this is not surprising. >>> Please explain limitations or where the script can actually be executed. That would be the

Re: [DOCS] pg_restore documentation

On Monday, June 26, 2017, wrote: > > pg_restore drupal_dump.sql -h > adjh4syhpk555s.cckxxqjsrxhd.us-east-1.rds.amazonaws.com -U someUser -W > yeahRight -d wm_drupal > > I get error: > > pg_restore: too many command-line arguments (first is > "yeahRight") > All -W does is force a prompt. There is

Re: [DOCS] ALTER SYSTEM is equal to editing postgresql.auto.conf, not postgres.conf

On Thu, Jul 13, 2017 at 3:53 AM, wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/9.6/static/config-setting.html > Description: > > > The already-mentioned ALTER SYSTEM command provides a SQL-accessible > means > of changing gl

Re: [DOCS] pg_dump "Access is denied" Windows 10

On Thu, Jul 20, 2017 at 6:37 PM, wrote: > Could you include in this documentation possible problems and fixes to this > because I can't find any. > ​tl;dr - the documentation is not a good place for such content.​ ​It would be helpful if you'd get diagnostic help on the -general mailing list fi

Re: [DOCS] recommending change to first example in 7.8.1

On Monday, July 24, 2017, wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/9.6/static/queries-with.html > Description: > > The first example in 7.8.1 shown below includes a field called > 'quantity' to > be summed in the primar

Re: [DOCS] Confused about a statement in WAL configs

On Mon, Jul 31, 2017 at 6:16 AM, wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/9.6/static/wal-configuration.html > Description: > > In this section: > > "At checkpoint time, all dirty data pages are flushed to disk and a > s

Re: [DOCS] Confused about a statement in WAL configs

On Tue, Aug 1, 2017 at 7:23 AM, Jeremy Finzel wrote: > > I *think* I follow now: before the checkpoint, the dirty data pages had > already been written to the WAL files, but not necessarily flushed to > disk. The checkpoint flushes them all to disk as well. > ​Yes, that it correct. David J.​

Re: [DOCS] "data" not "datums"

On Mon, Aug 7, 2017 at 1:15 PM, Peter Eisentraut < peter.eisentr...@2ndquadrant.com> wrote: > On 8/1/17 04:22, mahsh.bah...@gmail.com wrote: > > The following documentation comment has been logged on the website: > > > > Page: https://www.postgresql.org/docs/9.4/static/datatype-json.html > > Descr

Re: [DOCS] Further Clarification request

On Wed, Aug 9, 2017 at 6:25 AM, wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/9.6/static/sql-prepare.html > Description: > > https://www.postgresql.org/docs/9.6/static/sql-prepare.html > > The first example: I'd like to see

Re: [DOCS] Further Clarification request

On Wed, Aug 9, 2017 at 3:21 PM, Jym Morton wrote: > When I write software, and use a database I don’t need to escape literals > if I have a Prepared Statement. This is a major reason some of us use > Prepared Statements. So, when I looked at this page, I was unclear about > was whether it or n

Re: [DOCS] Further Clarification request

On Wed, Aug 9, 2017 at 4:03 PM, David G. Johnston < david.g.johns...@gmail.com> wrote: > On Wed, Aug 9, 2017 at 3:21 PM, Jym Morton wrote: > >> When I write software, and use a database I don’t need to escape literals >> if I have a Prepared Statement. This is a maj

Re: [DOCS] Syntax for changing owner on sequence is not correct

On Thu, Aug 10, 2017 at 5:37 AM, Peter Eisentraut < peter.eisentr...@2ndquadrant.com> wrote: > On 8/9/17 05:35, tarik.dolovac...@gmail.com wrote: > > The following documentation comment has been logged on the website: > > > > Page: https://www.postgresql.org/docs/8.4/static/sql-altersequence.html

Re: [DOCS] Postgres user lost his superuser authority

​ On Tue, Aug 15, 2017 at 5:39 AM, wrote: > The following documentation comment has been logged on the website: > We'd prefer that you not use the documentation comment feature for soliciting help with issues. You should email the pgsql-gene...@postgresql.org mailing list instead. If you do re

Re: [DOCS] Failing example for to_number()

On Mon, Aug 21, 2017 at 5:36 AM, Erwin Brandstetter wrote: > The manual suggests here: > > https://www.postgresql.org/docs/current/static/functions- > formatting.html#FUNCTIONS-FORMATTING-TABLE > > > to_number(text, text) | numeric convert string to numeric | to_number > ('12,454.8-', '99G999D9S

Re: [DOCS] Failing example for to_number()

On Mon, Aug 21, 2017 at 7:55 AM, Erwin Brandstetter wrote: > On top of this (separate issue?) ',' and '.' are ***not*** interpreted > according to the current LC_NUMERIC setting. I.e.: even with (example) > Austrian locale, ',' still is interpreted as group separator and '.' still > is the decima

Re: [DOCS] intarray - benefits over regular int[]?

On Mon, Aug 21, 2017 at 12:33 PM, wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/10/static/intarray.html > Description: > ​[...]​ > At the moment I am a little unclear whether intarray is effectively a > deprecated module,

Re: [DOCS] Syntax for changing owner on sequence is not correct

On Thu, Aug 24, 2017 at 11:25 AM, Tarik Dolovac wrote: > I am just telling you that in your officiall documentation i didn't find > that command. > ​What command? Both OWNED BY and OWNER TO are parts of the ALTER SEQUENCE command and written and described on the page you were reading when you ​

Re: [DOCS] mistype

On Fri, Aug 25, 2017 at 12:19 PM, wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/9.6/static/sql-expressions.html > Description: > > cite "The restriction about appearing only in the result list or > HAVING > clause applies wi

Re: [DOCS] Row Level Security Policies documentation doesn't mention lack of support for views

The CREATE VIEW documentation links to https://www.postgresql.org/docs/9.6/static/rules-privileges.html which covers this dynamic in considerable detail (and there is a blurb on the CREATE VIEW page as well), and specifically: "Relations that are used due to rules get checked against the privile

Re: [DOCS] Need help finding all possible parameters for wal_level

On Fri, Sep 1, 2017 at 7:46 AM, None wrote: > Well, so that's what doesn't make sense. Other documentation also > indicates a 'hot_standby' setting and I'm looking to see if it can do > 'warm_standby' as well. I was hoping for a complete list because it seems > scattered right now. > ​The docume

Re: [DOCS] 'alter sequence xxx start 200' do nothing

On Mon, Sep 4, 2017 at 11:51 PM, wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/9.5/static/functions-sequence.html > > Alter sequence public.xxx start with 200 > > It has no effect, without error message, but setval(200) work

Re: [DOCS] LOCAL and TIME ZONE in SET

On Mon, Sep 11, 2017 at 8:26 AM, Steve Crawford < scrawf...@pinpointresearch.com> wrote: > On Fri, Sep 8, 2017 at 1:05 PM, wrote: > >> The following documentation comment has been logged on the website: >> >> Page: https://www.postgresql.org/docs/9.5/static/sql-alterdatabase.html >> Description:

Re: [DOCS] 4.2.9. Type Casts - documentation improvement

On Tue, Sep 12, 2017 at 4:14 PM, Steve Atkins wrote: > > > On Sep 12, 2017, at 3:33 PM, Bruce Momjian wrote: > > > > On Tue, Sep 5, 2017 at 02:17:12AM +, artej...@gmail.com wrote: > >> The following documentation comment has been logged on the website: > >> > >> Page: https://www.postgresql

Re: [DOCS] Incorrect result in the Table 9-28. to_char examples

On Monday, September 11, 2017, wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/9.6/static/functions-formatting.html > Description: > > select to_char(3148.5, '9G999D999'); does not return what was > mentioned in > the table, W

Re: [DOCS] How to prompt for a value if a variable is not set

On Monday, September 18, 2017, wrote: > > But if the variable is not set, I want the script to prompt for > it. In version 10 this should be doable, we introduced \if conditionals. You might be able to hack up something via "\!" in 9.6 and earlier (haven't tried it myself). David J.

Re: [DOCS] "Comparison of Different Solutions"

On Tue, Sep 26, 2017 at 7:00 PM, Jaime Casanova < jaime.casan...@2ndquadrant.com> wrote: > On 31 May 2017 at 03:40, Tatsuo Ishii wrote: > > > > In "26.1 Comparison of Different Solutions", nothing is mentioned with > > logical replication. I think the section is the biggest picture for > > all hi

Re: [DOCS] Wrong COPY command synopsis

On Wed, Sep 27, 2017 at 4:01 AM, wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/9.1/static/sql-copy.html > Description: > > Postgres psql (PostgreSQL) 9.5.4 > > Wrong COPY command synopsis: > > 1. comma is not an options sepa

Re: [DOCS] Doc BUG and/or Change Request: Include Postgres's system columns in reserved words in docs, Chnage to previx sytem colums with 2 underscores?

On Tue, Oct 3, 2017 at 6:13 AM, Euler Taveira wrote: > 2017-10-02 22:30 GMT-03:00 dan d : > > Npgsql.PostgresException (0x80004005): 42701: column name "cmax" > conflicts > > with a system column name > > > > My first step was to google "Postgres Reserved Words" will eventually > get > > you to

Re: [DOCS] Doc BUG and/or Change Request: Include Postgres's system columns in reserved words in docs, Chnage to previx sytem colums with 2 underscores?

On Tue, Oct 3, 2017 at 10:34 AM, dan d wrote: > The fix is really simply prefix system reserved column names with one or > two underscores. Simple clean prevents the issue between user code and > database code... > The challenge isn't in making the fix (though it would likely be extremely tediou

Re: [DOCS] inappropriate word 'victim'

On Tue, Oct 3, 2017 at 12:53 PM, Joshua D. Drake wrote: > On 10/03/2017 12:38 PM, devguy...@gmail.com wrote: > >> The following documentation comment has been logged on the website: >> >> Page: https://www.postgresql.org/docs/9.6/static/manage-ag-dropdb.html >> Description: >> >> I am sure this w

Re: [DOCS] About installation of binary

On Tuesday, October 3, 2017, Echizenya, Noriyuki < echizenya.no...@jp.fujitsu.com> wrote: > > > For that reason I have looked up below for the source code download > destination. > https://www.postgresql.org/download/ > > The installation binaries are also released in the link in addition to the >

Re: [DOCS] 19.2. File Locations doesn't tell you the file locations!

On Fri, Oct 6, 2017 at 3:06 AM, wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/10/static/runtime-config- > file-locations.html > Description: > > In the latest documentation "Section 19.2. File Locations" tells > you how to >