Re: [DOCS] gen_random_uuid security not explicit in documentation
On 06/23/2017 04:23 AM, Michael Paquier wrote: On Fri, Jun 23, 2017 at 3:02 AM, Heikki Linnakangas wrote: I'm inclined to change gen_random_uuid() to throw an error if the server is built with --disable-strong-random, like gen_random_bytes() does. That way, they would behave the same. No obje
Re: [DOCS] Documentation still mentioning SSLv2 and SSLv3
On Mon, Jun 19, 2017 at 6:24 AM, Michael Paquier wrote: > Hi all, > > The documentation of libpq and sslinfo are still mentioning SSLv2 and > SSLv3, though such settings cannot be reach as they are not supported > anymore. Wouldn't it make sense to replace those mentions by TLSv1.*? > Please find
[DOCS] Confusing Trigger Docs.
The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/9.6/static/trigger-definition.html Description: https://www.postgresql.org/docs/devel/static/trigger-definition.html This sentence: "If an INSERT contains an ON CONFLICT DO UPDATE clause, i
Re: [DOCS] Synchronous logical replication?
Peter Eisentraut writes: > The reason for this confusion is that synchronous_commit has both a > local and a remote meaning, and in this case the local meaning on the > subscriber has an impact on the remote meaning of the publisher. And another, if I get it right, is that while asynchronous com
[DOCS] can't be both non-capturing and still capture
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/9.6/static/index.html
Description:
In postgresql-doc-9.5/html/functions-matching.html#POSIX-MATCHING-RULES:
SELECT regexp_matches('abc01234xyz',
'(?:(.*?)(\d+)(.*)){1,1
Re: [DOCS] Documentation still mentioning SSLv2 and SSLv3
On Tue, Jul 4, 2017 at 12:17 AM, Magnus Hagander wrote: > On Mon, Jun 19, 2017 at 6:24 AM, Michael Paquier > wrote: >> The documentation of libpq and sslinfo are still mentioning SSLv2 and >> SSLv3, though such settings cannot be reach as they are not supported >> anymore. Wouldn't it make sense
Re: [DOCS] can't be both non-capturing and still capture
s...@coolheads.com writes: > Here, the whole regexp is non-capturing, right, so how can the result be > reported as shown? No, the outer parens are non-capturing, but the ones inside them still are capturing parens. Perhaps it would clarify matters if you tried it with plain outer parens: =# SEL
