Fix check_srf_call_placement() to handle VALUES cases correctly.
INSERT ... VALUES with a single VALUES row is implemented quite differently
from the general VALUES case. A user-visible implication of that is that
we accept SRFs in the single-row case, but not in the multi-row case.
That's a hist
Fix NULL pointer dereference in tuplesort.c.
Oversight in commit e94568ecc. This could cause a crash when an external
datum tuplesort of a pass-by-value type required multiple passes.
Per report from Mithun Cy.
Peter Geoghegan
Discussion:
https://postgr.es/m/cad__oujuhfwfulgfst1fyhqub8n-xafjjh
Fix incorrect comparison due to bad merge
Noted by Fujii Masao
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/fcf708623e860b7a1efef11a5d5661900307b6fc
Modified Files
--
src/bin/pg_basebackup/pg_basebackup.c | 2 +-
1 file changed, 1 insertion(+), 1 delet
Make pg_basebackup use temporary replication slots
Temporary replication slots will be used by default when wal streaming
is used and no slot name is specified with -S. If a slot name is
specified, then a permanent slot with that name is used. If --no-slot is
specified, then no permanent or tempor
On Sat, Jan 14, 2017 at 12:07 AM, Robert Haas wrote:
> Fix cardinality estimates for parallel joins.
>
+ /*
+* In the case of a parallel plan, the row count needs to represent
+* the number of tuples processed per worker.
+*/
+ path->rows = clamp_row_est(path->
Fix typos in comments.
Masahiko Sawada
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/8fa6019b405f9d39539a77c6f5f11fe640ddf955
Modified Files
--
src/backend/storage/lmgr/condition_variable.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--
