Improve implementation of pg_attribute_always_inline.
Avoid compiler warnings on MSVC (which doesn't want to see both
__forceinline and inline) and ancient GCC (which doesn't have
__attribute__((always_inline))).
Don't force inline-ing when building at -O0, as the programmer is probably
hoping fo
doc: mention psql -l uses the 'postgres' database by default
Reported-by: Mark Wood
Bug: 14912
Discussion:
https://postgr.es/m/20171116171735.1474.30...@wrigleys.postgresql.org
Author: David G. Johnston
Backpatch-through: 10
Branch
--
REL_10_STABLE
Details
---
https://git.postgresq
doc: mention psql -l uses the 'postgres' database by default
Reported-by: Mark Wood
Bug: 14912
Discussion:
https://postgr.es/m/20171116171735.1474.30...@wrigleys.postgresql.org
Author: David G. Johnston
Backpatch-through: 10
Branch
--
master
Details
---
https://git.postgresql.org/p
Teach reparameterize_path() to handle AppendPaths.
If we're inside a lateral subquery, there may be no unparameterized paths
for a particular child relation of an appendrel, in which case we *must*
be able to create similarly-parameterized paths for each other child
relation, else the planner will
Teach reparameterize_path() to handle AppendPaths.
If we're inside a lateral subquery, there may be no unparameterized paths
for a particular child relation of an appendrel, in which case we *must*
be able to create similarly-parameterized paths for each other child
relation, else the planner will
Teach reparameterize_path() to handle AppendPaths.
If we're inside a lateral subquery, there may be no unparameterized paths
for a particular child relation of an appendrel, in which case we *must*
be able to create similarly-parameterized paths for each other child
relation, else the planner will
Teach reparameterize_path() to handle AppendPaths.
If we're inside a lateral subquery, there may be no unparameterized paths
for a particular child relation of an appendrel, in which case we *must*
be able to create similarly-parameterized paths for each other child
relation, else the planner will
Teach reparameterize_path() to handle AppendPaths.
If we're inside a lateral subquery, there may be no unparameterized paths
for a particular child relation of an appendrel, in which case we *must*
be able to create similarly-parameterized paths for each other child
relation, else the planner will
Teach reparameterize_path() to handle AppendPaths.
If we're inside a lateral subquery, there may be no unparameterized paths
for a particular child relation of an appendrel, in which case we *must*
be able to create similarly-parameterized paths for each other child
relation, else the planner will
Remove unnecessary include
autovacuum.c no longer needs dsa.h, since commit 31ae1638ce3.
Author: Masahiko Sawada
Discussion:
https://postgr.es/m/cad21aocwvyyxrvdanshwwwewjh5teawakj_2gqrhhukg+ob...@mail.gmail.com
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/95be5
Remove unnecessary include
autovacuum.c no longer needs dsa.h, since commit 31ae1638ce3.
Author: Masahiko Sawada
Discussion:
https://postgr.es/m/cad21aocwvyyxrvdanshwwwewjh5teawakj_2gqrhhukg+ob...@mail.gmail.com
Branch
--
REL_10_STABLE
Details
---
https://git.postgresql.org/pg/commitdif
Documentation fix: pg_ctl no longer makes connection attempts.
Overlooked in commit f13ea95f9. Noted by Nick Barnes.
Discussion: https://postgr.es/m/20180123093723.7407.3...@wrigleys.postgresql.org
Branch
--
REL_10_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/5ca17d655f9
Documentation fix: pg_ctl no longer makes connection attempts.
Overlooked in commit f13ea95f9. Noted by Nick Barnes.
Discussion: https://postgr.es/m/20180123093723.7407.3...@wrigleys.postgresql.org
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/c9707d9413b171a6f0
pgbench: Remove accidental garbage in test file
Author: Fabien COELHO
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/f9bbd46adbf350ba9e99a808f2c759e4aab9ea70
Modified Files
--
src/bin/pgbench/t/001_pgbench_with_server.pl | 6 --
1 file changed, 6 d
Update obsolete sentence in README.parallel.
Since 9.6, heavyweight locking is not an abstract and unhandled
concern of the parallel machinery, but rather something to which
we have a specific approach.
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/28e04155f17cabd
Report an ERROR if a parallel worker fails to start properly.
Commit 28724fd90d2f85a0573a8107b48abad062a86d83 fixed things so that
if a background worker fails to start due to fork() failure or because
it is terminated before startup succeeds, BGWH_STOPPED will be
reported. However, that only hel
Report an ERROR if a parallel worker fails to start properly.
Commit 28724fd90d2f85a0573a8107b48abad062a86d83 fixed things so that
if a background worker fails to start due to fork() failure or because
it is terminated before startup succeeds, BGWH_STOPPED will be
reported. However, that only hel
Report an ERROR if a parallel worker fails to start properly.
Commit 28724fd90d2f85a0573a8107b48abad062a86d83 fixed things so that
if a background worker fails to start due to fork() failure or because
it is terminated before startup succeeds, BGWH_STOPPED will be
reported. However, that only hel
In pg_dump, force reconnection after issuing ALTER DATABASE SET command(s).
The folly of not doing this was exposed by the buildfarm: in some cases,
the GUC settings applied through ALTER DATABASE SET may be essential to
interpreting the reloaded data correctly. Another argument why we can't
real
doc: simplify intermediate certificate mention in libpq docs
Backpatch-through: 9.3
Branch
--
REL9_5_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/29aecb94a3d94276b06d67b760d7de498cc0f36e
Modified Files
--
doc/src/sgml/libpq.sgml | 9 -
1 file changed,
doc: simplify intermediate certificate mention in libpq docs
Backpatch-through: 9.3
Branch
--
REL9_6_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/cda1ba3f3bebd5a61bef981773c4cbb97ad33590
Modified Files
--
doc/src/sgml/libpq.sgml | 9 -
1 file changed,
doc: simplify intermediate certificate mention in libpq docs
Backpatch-through: 9.3
Branch
--
REL_10_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/5aaa8f4b8f78ed22505a1b0350ee1aafb3db
Modified Files
--
doc/src/sgml/libpq.sgml | 9 -
1 file changed,
doc: simplify intermediate certificate mention in libpq docs
Backpatch-through: 9.3
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/a541dbb6fa389bb0ffdd24a403bc6d276d77a074
Modified Files
--
doc/src/sgml/libpq.sgml | 9 -
1 file changed, 4 inser
doc: simplify intermediate certificate mention in libpq docs
Backpatch-through: 9.3
Branch
--
REL9_3_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/b049ae3a3a3d05f65490097f8fe05ef8354365fd
Modified Files
--
doc/src/sgml/libpq.sgml | 9 -
1 file changed,
doc: simplify intermediate certificate mention in libpq docs
Backpatch-through: 9.3
Branch
--
REL9_4_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/a0950b1b96477fd64e210a0816e68d1c0db2053a
Modified Files
--
doc/src/sgml/libpq.sgml | 9 -
1 file changed,
On Sat, Jan 20, 2018 at 2:03 AM, Robert Haas wrote:
> Allow UPDATE to move rows between partitions.
>
+If an UPDATE on a partitioned table causes a row to move
+to another partition, it will be performed as a DELETE
+from the original partition followed by an INSERT into
+the new
Move EDH support to common files
The EDH support is not really specific to the OpenSSL implementation, so
move the support and documentation comments to common files.
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/573bd08b99e277026e87bb55ae69c489fab321b8
Modified
Move SSL API comments to header files
Move the documentation of the SSL API calls are supposed to do into the
headers files, instead of keeping them in the files for the OpenSSL
implementation. That way, they don't have to be duplicated or be
inconsistent when other implementations are added.
Br
Split out documentation of SSL parameters into their own section
Split the "Authentication and Security" section into two separate
sections "Authentication" and "SSL". The latter part has gotten much
longer over time, and doesn't primarily have to do with authentication.
Also, the row_security p
Extract common bits from OpenSSL implementation
Some things in be-secure-openssl.c and fe-secure-openssl.c were not
actually specific to OpenSSL but could also be used by other
implementations. In order to avoid copy-and-pasting, move some of that
code to common files.
Branch
--
master
Deta
Add installcheck support to more test suites
Several of the test suites under src/test/ were missing an installcheck
target.
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/f5da5683a86e9fc42fdf3eae2da8b096bda76a8a
Modified Files
--
src/test/authenticati
31 matches
Mail list logo
