Re: [DOCS] pg_archivecleanup docs

On 8/5/16 11:53 AM, Jeff Janes wrote: > I think the documentation for the -x option is confusing: > > -x extension > > When using the program as a standalone utility, provide an extension > that will be stripped from all file names before deciding if they > should be deleted. This is typically us

Re: [DOCS] Several repeated words

On 8/16/16 12:02 PM, Alexander Law wrote: > There are some occurrences of repeated words in the docs. Patches attached. Fixed in master and 9.6 -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-

Re: [DOCS] missing SQL BEGIN in example ECPG Program Accessing Large Objects

On 8/8/16 8:37 AM, tma...@gmx.de wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/9.5/static/ecpg-lo.html > Description: > > Example 33-2. ECPG Program Accessing Large Objects > > after >EXEC SQL CONNECT > > missing

Re: [DOCS] Soundex

On 8/8/16 7:21 PM, ch...@martin.cc wrote: > soundex/metaphone page: > https://www.postgresql.org/docs/current/static/fuzzystrmatch.html > > It would be good to include that you need to install the fuzzyystrmatch > extension We don't explain for each module individually that you need to install it

[DOCS] Broken Link

Hi, Just wanted to let you know about a link that seems to be broken on this page http://tpchihuahua.uach.mx/cvsup.html. It is this link http://www.research.digital.com/SRC/modula-3/html/home.html, but the site doesn’t seem to be active any more. I thought you might want to update your page.

[DOCS] Several repeated words

Hello, There are some occurrences of repeated words in the docs. Patches attached. Also, please consider fixing 'and and' and 'the the' in the source code and regression test comments. Best regards, Alexander diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml index 66fbe44..6

Re: [DOCS] Row locking within a SELECT statement

x...@linux.gr writes: > In order to avoid concurrent manipulation of rows, I do issue a "SELECT > .. > FOR UPDATE" on the sets of rows, before UPDATEing them (because UPDATEs > cannot be ordered). > transaction A { > SELECT .. FROM alerts WHERE FOR UPDATE; > ... decide ... > UPDATE aler

Re: [DOCS] Outdated sentence in the pg_am description

Alexander Law writes: > It seems, that the pg_am description contains a sentence that is not > valid anymore. Patch attached. Fixed, thanks. regards, tom lane -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://

Re: [DOCS] Row locking within a SELECT statement

Στις Τρι 16 Αυγ 2016 11:23:59 π.μ. Marko Tiikkaja έγραψε: > On 2016-08-16 08:19, x...@linux.gr wrote: > > In order to avoid concurrent manipulation of rows, I do issue a > > "SELECT .. FOR UPDATE" on the sets of rows, before UPDATEing > > them (because UPDATEs cannot be ordered). > > Yeah, but FOR

Re: [DOCS] Row locking within a SELECT statement

On 2016-08-16 08:19, x...@linux.gr wrote: In order to avoid concurrent manipulation of rows, I do issue a "SELECT .. FOR UPDATE" on the sets of rows, before UPDATEing them (because UPDATEs cannot be ordered). Yeah, but FOR UPDATEs are not ordered either unless you use ORDER BY, which you didn'

[DOCS] Outdated sentence in the pg_am description

Hello, It seems, that the pg_am description contains a sentence that is not valid anymore. Patch attached. Best regards, Alexander diff --git a/doc/src/sgml/indexam.sgml b/doc/src/sgml/indexam.sgml index b59cd03..0704926 100644 --- a/doc/src/sgml/indexam.sgml +++ b/doc/src/sgml/indexam.sgml @