Disable parallel query by default.
Per discussion, set the default value of max_parallel_workers_per_gather
to 0 in 9.6 only. We'll leave it enabled in master so that it gets
more testing and in the hope that it can be enable by default in v10.
Branch
--
REL9_6_STABLE
Details
---
http:/
Doc: remove out-of-date claim that pg_am rows must be inserted by hand.
Commit 473b93287 added a sentence about that, but neglected to remove
the adjacent sentence it had falsified. Per Alexander Law.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/8fc571b7dd9fa1659
Doc: remove out-of-date claim that pg_am rows must be inserted by hand.
Commit 473b93287 added a sentence about that, but neglected to remove
the adjacent sentence it had falsified. Per Alexander Law.
Branch
--
REL9_6_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/23e0d97d1c
Doc: copy-editing in create_access_method.sgml.
Improve shaky English grammar. And markup.
Branch
--
REL9_6_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/d95a7c3fbcfd5e65802f7fb0bee31a914160d9ed
Modified Files
--
doc/src/sgml/ref/create_access_method.sgml | 27
Doc: copy-editing in create_access_method.sgml.
Improve shaky English grammar. And markup.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/9b002cc9fec557fcfe17d67f55b53804447230e5
Modified Files
--
doc/src/sgml/ref/create_access_method.sgml | 27 +++
Remove separate version numbering for ecpg preprocessor.
Once upon a time, it made sense for the ecpg preprocessor to have its
own version number, because it used a manually-maintained grammar that
wasn't always in sync with the core grammar. But those days are
thankfully long gone, leaving only
Fix possible crash due to incorrect allocation context.
Commit af33039317ddc4a0e38a02e2255c2bf453115fd2 aimed to reduce
leakage from tqueue.c, which is good. Unfortunately, by changing the
memory context in which all of gather_readnext() executes, it also
changed the context in which ExecShutdown
Fix possible crash due to incorrect allocation context.
Commit af33039317ddc4a0e38a02e2255c2bf453115fd2 aimed to reduce
leakage from tqueue.c, which is good. Unfortunately, by changing the
memory context in which all of gather_readnext() executes, it also
changed the context in which ExecShutdown
Automate the maintenance of SO_MINOR_VERSION for our shared libraries.
Up to now we've manually adjusted these numbers in several different
Makefiles at the start of each development cycle. While that's not
much work, it's easily forgotten, so let's get rid of it by setting
the SO_MINOR_VERSION v
Fix typos
From: Alexander Law
Branch
--
REL9_6_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/7c7630c2022156d54adf6c1d27c30f2b75138f03
Modified Files
--
doc/src/sgml/release-9.6.sgml| 2 +-
doc/src/sgml/runtime.sgml| 2 +-
src/backend/a
Fix typos
From: Alexander Law
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/f0fe1c8f70bacb65513f1cbaea14eb384d346ee8
Modified Files
--
doc/src/sgml/release-9.6.sgml| 2 +-
doc/src/sgml/runtime.sgml| 2 +-
src/backend/access/t
doc: Remove some confusion from pg_archivecleanup doc
From: Jeff Janes
Branch
--
REL9_6_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/203bf7f4078451c2a75c21251882227cf67e1cd3
Modified Files
--
doc/src/sgml/ref/pgarchivecleanup.sgml | 2 +-
1 file changed, 1 inse
doc: Remove some confusion from pg_archivecleanup doc
From: Jeff Janes
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/639166641102871e09f9c4aebc71df57566a0a4a
Modified Files
--
doc/src/sgml/ref/pgarchivecleanup.sgml | 2 +-
1 file changed, 1 insertion(+
On 8/14/16 3:06 PM, Tom Lane wrote:
> Remove bogus dependencies on NUMERIC_MAX_PRECISION.
Some compilers are reporting a warning
dbsize.c:768:3: warning: ignoring return value of ‘strtol’, declared
with attribute warn_unused_result [-Wunused-result]
from this change.
--
Peter Eisentraut
Fix assorted places in psql to print version numbers >= 10 in new style.
This is somewhat cosmetic, since as long as you know what you are looking
at, "10.0" is a serviceable substitute for "10". But there is a potential
for confusion between version numbers with minor numbers and those without
-
Fix assorted places in psql to print version numbers >= 10 in new style.
This is somewhat cosmetic, since as long as you know what you are looking
at, "10.0" is a serviceable substitute for "10". But there is a potential
for confusion between version numbers with minor numbers and those without
-
Fix assorted places in psql to print version numbers >= 10 in new style.
This is somewhat cosmetic, since as long as you know what you are looking
at, "10.0" is a serviceable substitute for "10". But there is a potential
for confusion between version numbers with minor numbers and those without
-
Fix assorted places in psql to print version numbers >= 10 in new style.
This is somewhat cosmetic, since as long as you know what you are looking
at, "10.0" is a serviceable substitute for "10". But there is a potential
for confusion between version numbers with minor numbers and those without
-
Fix assorted places in psql to print version numbers >= 10 in new style.
This is somewhat cosmetic, since as long as you know what you are looking
at, "10.0" is a serviceable substitute for "10". But there is a potential
for confusion between version numbers with minor numbers and those without
-
Peter Eisentraut writes:
> On 8/14/16 3:06 PM, Tom Lane wrote:
>> Remove bogus dependencies on NUMERIC_MAX_PRECISION.
> Some compilers are reporting a warning
> dbsize.c:768:3: warning: ignoring return value of âstrtolâ, declared
> with attribute warn_unused_result [-Wunused-result]
Oh fchr
Suppress -Wunused-result warning for strtol().
I'm not sure which bozo thought it's a problem to use strtol() only
for its endptr result, but silence the warning using same method
used elsewhere.
Report:
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/4bc4cfe3bd186
Suppress -Wunused-result warning for strtol().
I'm not sure which bozo thought it's a problem to use strtol() only
for its endptr result, but silence the warning using same method
used elsewhere.
Report:
Branch
--
REL9_6_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/f1222a
Improve parsetree representation of special functions such as CURRENT_DATE.
We implement a dozen or so parameterless functions that the SQL standard
defines special syntax for. Up to now, that was done by converting them
into more or less ad-hoc constructs such as "'now'::text::date". That's
mes
docs: my third pass over the 9.6 release notes
Backpatch-through: 9.6
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/d125d25790901683d5ad16bfc96e9de4ccc9a581
Modified Files
--
doc/src/sgml/release-9.6.sgml | 628 ++--
docs: my third pass over the 9.6 release notes
Backpatch-through: 9.6
Branch
--
REL9_6_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/dd028e904c67dae5f5d51da73628a8bd3cb1f5f1
Modified Files
--
doc/src/sgml/release-9.6.sgml | 628 ++---
25 matches
Mail list logo
