Fix compiler error introduced by 5386bfb9c1f.
Per buildfarm member wrasse, void function cannot return a value.
This only affects v13-v17, where an ABI-compatible wrapper function
was added.
Backpatch-through: 13-17
Branch
--
REL_14_STABLE
Details
---
https://git.postgresql.org/pg/commi
to do this
can silently break replication.
Author: Zhijie Hou
Reviewed-by: Ashutosh Bapat
Reviewed-by: Dean Rasheed
Tested-by: Chao Li
Discussion:
https://postgr.es/m/os3pr01mb57180c87e43a679a730482df94...@os3pr01mb5718.jpnprd01.prod.outlook.com
Backpatch-through: 15
Branch
to do this
can silently break replication.
Author: Zhijie Hou
Reviewed-by: Ashutosh Bapat
Reviewed-by: Dean Rasheed
Tested-by: Chao Li
Discussion:
https://postgr.es/m/os3pr01mb57180c87e43a679a730482df94...@os3pr01mb5718.jpnprd01.prod.outlook.com
Backpatch-through: 15
Branch
Fix compiler error introduced by 5386bfb9c1f.
Per buildfarm member wrasse, void function cannot return a value.
This only affects v13-v17, where an ABI-compatible wrapper function
was added.
Backpatch-through: 13-17
Branch
--
REL_13_STABLE
Details
---
https://git.postgresql.org/pg/commi
Fix compiler error introduced by 5386bfb9c1f.
Per buildfarm member wrasse, void function cannot return a value.
This only affects v13-v17, where an ABI-compatible wrapper function
was added.
Backpatch-through: 13-17
Branch
--
REL_16_STABLE
Details
---
https://git.postgresql.org/pg/commi
Fix compiler error introduced by 5386bfb9c1f.
Per buildfarm member wrasse, void function cannot return a value.
This only affects v13-v17, where an ABI-compatible wrapper function
was added.
Backpatch-through: 13-17
Branch
--
REL_15_STABLE
Details
---
https://git.postgresql.org/pg/commi
Fix compiler error introduced by 5386bfb9c1f.
Per buildfarm member wrasse, void function cannot return a value.
This only affects v13-v17, where an ABI-compatible wrapper function
was added.
Backpatch-through: 13-17
Branch
--
REL_17_STABLE
Details
---
https://git.postgresql.org/pg/commi
to do this
can silently break replication.
Author: Zhijie Hou
Reviewed-by: Ashutosh Bapat
Reviewed-by: Dean Rasheed
Tested-by: Chao Li
Discussion:
https://postgr.es/m/os3pr01mb57180c87e43a679a730482df94...@os3pr01mb5718.jpnprd01.prod.outlook.com
Backpatch-through: 15
Branch
signature.
Author: Zhijie Hou
Reviewed-by: Ashutosh Bapat
Reviewed-by: Dean Rasheed
Tested-by: Chao Li
Discussion:
https://postgr.es/m/os3pr01mb57180c87e43a679a730482df94...@os3pr01mb5718.jpnprd01.prod.outlook.com
Backpatch-through: 13
Branch
--
master
Details
---
https
signature.
Author: Zhijie Hou
Reviewed-by: Ashutosh Bapat
Reviewed-by: Dean Rasheed
Tested-by: Chao Li
Discussion:
https://postgr.es/m/os3pr01mb57180c87e43a679a730482df94...@os3pr01mb5718.jpnprd01.prod.outlook.com
Backpatch-through: 13
Branch
--
REL_14_STABLE
Details
---
https
signature.
Author: Zhijie Hou
Reviewed-by: Ashutosh Bapat
Reviewed-by: Dean Rasheed
Tested-by: Chao Li
Discussion:
https://postgr.es/m/os3pr01mb57180c87e43a679a730482df94...@os3pr01mb5718.jpnprd01.prod.outlook.com
Backpatch-through: 13
Branch
--
REL_13_STABLE
Details
---
https
signature.
Author: Zhijie Hou
Reviewed-by: Ashutosh Bapat
Reviewed-by: Dean Rasheed
Tested-by: Chao Li
Discussion:
https://postgr.es/m/os3pr01mb57180c87e43a679a730482df94...@os3pr01mb5718.jpnprd01.prod.outlook.com
Backpatch-through: 13
Branch
--
REL_17_STABLE
Details
---
https
to be checked by the
selectivity estimation functions.
Author: Dean Rasheed
Reviewed-by: Tom Lane
Reviewed-by: Noah Misch
Backpatch-through: 13
Security: CVE-2025-8713
Branch
--
REL_13_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/533211ded37aed55c715e9e237209a3deef4
to be checked by the
selectivity estimation functions.
Author: Dean Rasheed
Reviewed-by: Tom Lane
Reviewed-by: Noah Misch
Backpatch-through: 13
Security: CVE-2025-8713
Branch
--
REL_14_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/afe38fb6abb8ef364191201f577a5a638ba5
to be checked by the
selectivity estimation functions.
Author: Dean Rasheed
Reviewed-by: Tom Lane
Reviewed-by: Noah Misch
Backpatch-through: 13
Security: CVE-2025-8713
Branch
--
REL_17_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/a85eddab23f17bce333d7d9481f528d7ba78
to be checked by the
selectivity estimation functions.
Author: Dean Rasheed
Reviewed-by: Tom Lane
Reviewed-by: Noah Misch
Backpatch-through: 13
Security: CVE-2025-8713
Branch
--
REL_16_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/7e86da539d18bc29377a3882b9945dfbeb37
to be checked by the
selectivity estimation functions.
Author: Dean Rasheed
Reviewed-by: Tom Lane
Reviewed-by: Noah Misch
Backpatch-through: 13
Security: CVE-2025-8713
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/22424953cded3f83f0382383773eaf36eb1abda9
Modified File
to be checked by the
selectivity estimation functions.
Author: Dean Rasheed
Reviewed-by: Tom Lane
Reviewed-by: Noah Misch
Backpatch-through: 13
Security: CVE-2025-8713
Branch
--
REL_18_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/64f77c6a65cb6a0731e59acbfab1dd1663b1
to be checked by the
selectivity estimation functions.
Author: Dean Rasheed
Reviewed-by: Tom Lane
Reviewed-by: Noah Misch
Backpatch-through: 13
Security: CVE-2025-8713
Branch
--
REL_15_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/415badc138189a6ecfe3b664dc900af74134
those work more
generally would require rolling our own higher precision 128-bit
division, which isn't supported for now.
Author: Dean Rasheed
Reviewed-by: John Naylor
Discussion:
https://postgr.es/m/caezatcwgbmc9zwkmyqqpaqz2x6gaamyrb+rnmsuncdmcl2m...@mail.gmail.com
Branch
--
m
, leading to more compact and efficient
code. The actual performance gain is quite modest, but it seems worth
it to improve the code's readability.
Author: Dean Rasheed
Reviewed-by: John Naylor
Discussion:
https://postgr.es/m/caezatcwgbmc9zwkmyqqpaqz2x6gaamyrb+rnmsuncdmcl2m...@mail.gmai
for carry in int128_add_int64() can be written in
much the same way, but with an extra term to compensate for the sign
of the value being added. Again, on modern compilers this leads to
branchless code, often identical to the native 128-bit integer
addition machine code.
Author: Dean Rasheed
Reviewed-by
separate parts of the file.
This improves readability and maintainability, making it easier to
compare the native and non-native implementations, and avoiding the
need to duplicate every function comment and declaration.
Author: Dean Rasheed
Reviewed-by: John Naylor
Discussion:
https://postgr.es
Fix printf format specfiers in test_int128 module.
Compiler warnings introduced by 8c7445a0081.
Author: Dean Rasheed
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/811633105a38bc40ff2f75879a4b9a1113bb0347
Modified Files
--
src/test/modules
ver setting and checking half of
each 128-bit integer value.
Author: Dean Rasheed
Reviewed-by: John Naylor
Discussion:
https://postgr.es/m/caezatcwgbmc9zwkmyqqpaqz2x6gaamyrb+rnmsuncdmcl2m...@mail.gmail.com
Branch
--
master
Details
---
https://git.postgresql.or
Fix typo in create_index.sql.
Introduced by 578b229718e.
Author: Dean Rasheed
Reviewed-by: Tender Wang
Discussion:
https://postgr.es/m/caezatcv_czrsopmf1gbhq7xtmyrv6ke7vicbd6b81wf7gft...@mail.gmail.com
Backpatch-through: 13
Branch
--
REL_17_STABLE
Details
---
https
Fix typo in create_index.sql.
Introduced by 578b229718e.
Author: Dean Rasheed
Reviewed-by: Tender Wang
Discussion:
https://postgr.es/m/caezatcv_czrsopmf1gbhq7xtmyrv6ke7vicbd6b81wf7gft...@mail.gmail.com
Backpatch-through: 13
Branch
--
REL_14_STABLE
Details
---
https
Fix typo in create_index.sql.
Introduced by 578b229718e.
Author: Dean Rasheed
Reviewed-by: Tender Wang
Discussion:
https://postgr.es/m/caezatcv_czrsopmf1gbhq7xtmyrv6ke7vicbd6b81wf7gft...@mail.gmail.com
Backpatch-through: 13
Branch
--
REL_15_STABLE
Details
---
https
Fix typo in create_index.sql.
Introduced by 578b229718e.
Author: Dean Rasheed
Reviewed-by: Tender Wang
Discussion:
https://postgr.es/m/caezatcv_czrsopmf1gbhq7xtmyrv6ke7vicbd6b81wf7gft...@mail.gmail.com
Backpatch-through: 13
Branch
--
REL_13_STABLE
Details
---
https
Fix typo in create_index.sql.
Introduced by 578b229718e.
Author: Dean Rasheed
Reviewed-by: Tender Wang
Discussion:
https://postgr.es/m/caezatcv_czrsopmf1gbhq7xtmyrv6ke7vicbd6b81wf7gft...@mail.gmail.com
Backpatch-through: 13
Branch
--
REL_16_STABLE
Details
---
https
Fix typo in create_index.sql.
Introduced by 578b229718e.
Author: Dean Rasheed
Reviewed-by: Tender Wang
Discussion:
https://postgr.es/m/caezatcv_czrsopmf1gbhq7xtmyrv6ke7vicbd6b81wf7gft...@mail.gmail.com
Backpatch-through: 13
Branch
--
master
Details
---
https://git.postgresql.org/pg
Fix typo in create_index.sql.
Introduced by 578b229718e.
Author: Dean Rasheed
Reviewed-by: Tender Wang
Discussion:
https://postgr.es/m/caezatcv_czrsopmf1gbhq7xtmyrv6ke7vicbd6b81wf7gft...@mail.gmail.com
Backpatch-through: 13
Branch
--
REL_18_STABLE
Details
---
https
in
v17 (though not in v18, which is still in beta).
Bug: #18986
Reported-by: Yaroslav Syrytsia
Author: Dean Rasheed
Reviewed-by: Michael Paquier
Discussion: https://postgr.es/m/18986-e7a8aac3d339f...@postgresql.org
Backpatch-through: 17
Branch
--
REL_18_STABLE
Details
---
in
v17 (though not in v18, which is still in beta).
Bug: #18986
Reported-by: Yaroslav Syrytsia
Author: Dean Rasheed
Reviewed-by: Michael Paquier
Discussion: https://postgr.es/m/18986-e7a8aac3d339f...@postgresql.org
Backpatch-through: 17
Branch
--
REL_17_STABLE
Details
---
in
v17 (though not in v18, which is still in beta).
Bug: #18986
Reported-by: Yaroslav Syrytsia
Author: Dean Rasheed
Reviewed-by: Michael Paquier
Discussion: https://postgr.es/m/18986-e7a8aac3d339f...@postgresql.org
Backpatch-through: 17
Branch
--
master
Details
---
https://git.postgresql.
doc: Updates for RETURNING OLD/NEW.
Fix a couple of sentences in the documentation that were missed in
commit 80feb727c8.
Author: Dean Rasheed
Reviewed-by: Robert Treat
Discussion:
https://postgr.es/m/caezatcucqadjuapzsjpf2b6hfj6agouwefrvh8ht3uzoqqw...@mail.gmail.com
Branch
--
master
doc: Fix indentation of MERGE synopsis.
The convention in the documentation for other SQL commands is to
indent continuation lines and sub-clauses in the "Synopsis" section by
4 spaces, so do the same for MERGE.
Author: Dean Rasheed
Reviewed-by: Nathan Bossart
Discussion:
https://p
doc: Fix indentation of MERGE synopsis.
The convention in the documentation for other SQL commands is to
indent continuation lines and sub-clauses in the "Synopsis" section by
4 spaces, so do the same for MERGE.
Author: Dean Rasheed
Reviewed-by: Nathan Bossart
Discussion:
https://p
doc: Fix indentation of MERGE synopsis.
The convention in the documentation for other SQL commands is to
indent continuation lines and sub-clauses in the "Synopsis" section by
4 spaces, so do the same for MERGE.
Author: Dean Rasheed
Reviewed-by: Nathan Bossart
Discussion:
https://p
doc: Fix indentation of MERGE synopsis.
The convention in the documentation for other SQL commands is to
indent continuation lines and sub-clauses in the "Synopsis" section by
4 spaces, so do the same for MERGE.
Author: Dean Rasheed
Reviewed-by: Nathan Bossart
Discussion:
https://p
to fully initialize rootResultRelInfo if the MERGE has
INSERT actions and the target table is a plain inheritance parent.
Backpatch to v15, where MERGE was introduced.
Reported-by: Andres Freund
Author: Dean Rasheed
Reviewed-by: Jian He
Reviewed-by: Tender Wang
Discussion:
to fully initialize rootResultRelInfo if the MERGE has
INSERT actions and the target table is a plain inheritance parent.
Backpatch to v15, where MERGE was introduced.
Reported-by: Andres Freund
Author: Dean Rasheed
Reviewed-by: Jian He
Reviewed-by: Tender Wang
Discussion:
to fully initialize rootResultRelInfo if the MERGE has
INSERT actions and the target table is a plain inheritance parent.
Backpatch to v15, where MERGE was introduced.
Reported-by: Andres Freund
Author: Dean Rasheed
Reviewed-by: Jian He
Reviewed-by: Tender Wang
Discussion:
to fully initialize rootResultRelInfo if the MERGE has
INSERT actions and the target table is a plain inheritance parent.
Backpatch to v15, where MERGE was introduced.
Reported-by: Andres Freund
Author: Dean Rasheed
Reviewed-by: Jian He
Reviewed-by: Tender Wang
Discussion:
isely what the default text search parser
recognises as valid XML tags, since that's what determines which XML
tags ts_headline() will remove.
Reported-by: Richard Neill
Author: Dean Rasheed
Reviewed-by: Noah Misch
Backpatch-through: 13
Branch
--
REL_17_STABLE
Details
---
isely what the default text search parser
recognises as valid XML tags, since that's what determines which XML
tags ts_headline() will remove.
Reported-by: Richard Neill
Author: Dean Rasheed
Reviewed-by: Noah Misch
Backpatch-through: 13
Branch
--
REL_16_STABLE
Details
---
isely what the default text search parser
recognises as valid XML tags, since that's what determines which XML
tags ts_headline() will remove.
Reported-by: Richard Neill
Author: Dean Rasheed
Reviewed-by: Noah Misch
Backpatch-through: 13
Branch
--
REL_13_STABLE
Details
---
isely what the default text search parser
recognises as valid XML tags, since that's what determines which XML
tags ts_headline() will remove.
Reported-by: Richard Neill
Author: Dean Rasheed
Reviewed-by: Noah Misch
Backpatch-through: 13
Branch
--
master
Details
---
https://git.post
isely what the default text search parser
recognises as valid XML tags, since that's what determines which XML
tags ts_headline() will remove.
Reported-by: Richard Neill
Author: Dean Rasheed
Reviewed-by: Noah Misch
Backpatch-through: 13
Branch
--
REL_14_STABLE
Details
---
isely what the default text search parser
recognises as valid XML tags, since that's what determines which XML
tags ts_headline() will remove.
Reported-by: Richard Neill
Author: Dean Rasheed
Reviewed-by: Noah Misch
Backpatch-through: 13
Branch
--
REL_15_STABLE
Details
---
Fix MERGE with DO NOTHING actions into a partitioned table.
ExecInitPartitionInfo() duplicates much of the logic in
ExecInitMerge(), except that it failed to handle DO NOTHING
actions. This would cause an "unknown action in MERGE WHEN clause"
error if a MERGE with any DO NOTHING actions attempted
Fix MERGE with DO NOTHING actions into a partitioned table.
ExecInitPartitionInfo() duplicates much of the logic in
ExecInitMerge(), except that it failed to handle DO NOTHING
actions. This would cause an "unknown action in MERGE WHEN clause"
error if a MERGE with any DO NOTHING actions attempted
Fix MERGE with DO NOTHING actions into a partitioned table.
ExecInitPartitionInfo() duplicates much of the logic in
ExecInitMerge(), except that it failed to handle DO NOTHING
actions. This would cause an "unknown action in MERGE WHEN clause"
error if a MERGE with any DO NOTHING actions attempted
Fix MERGE with DO NOTHING actions into a partitioned table.
ExecInitPartitionInfo() duplicates much of the logic in
ExecInitMerge(), except that it failed to handle DO NOTHING
actions. This would cause an "unknown action in MERGE WHEN clause"
error if a MERGE with any DO NOTHING actions attempted
Add support for gamma() and lgamma() functions.
These are useful general-purpose math functions which are included in
POSIX and C99, and are commonly included in other math libraries, so
expose them as SQL-callable functions.
Author: Dean Rasheed
Reviewed-by: Stepan Neretin
Reviewed-by: Peter
)::bytea -> \xfb2e
Author: Aleksander Alekseev
Reviewed-by: Joel Jacobson
Reviewed-by: Yugo Nagata
Reviewed-by: Peter Eisentraut
Reviewed-by: Michael Paquier
Reviewed-by: Dean Rasheed
Discussion:
https://postgr.es/m/CAJ7c6TPtOp6%2BkFX5QX3fH1SVr7v65uHr-7yEJ%3DGMGQi5uhGtcA%40mail.gmail.
Fix parsing of qualified relation names in RETURNING.
Given a qualified refname, refnameNamespaceItem() will search for a
matching namespace item by relation OID, rather than by name. Commit
80feb727c8 broke this by adding additional namespace items for OLD and
NEW in the RETURNING list, which hav
le
changes the command type. Therefore, we put no restrictions on the use
of old and new in any DML queries.
Dean Rasheed, reviewed by Jian He and Jeff Davis.
Discussion:
https://postgr.es/m/CAEZATCWx0J0-v=Qjc6gXzR=KtsdvAE7Ow=D=mu50agoe+pv...@mail.gmail.com
lently "\df+x") will produce a list of functions,
with additional details, in expanded mode.
This works with all \d* meta-commands, plus \l, \z, and \lo_list, with
the one exception that the expanded mode option "x" cannot be appended
to "\d" by itself, since "\dx
Consistently spell "leakproof" without a hyphen.
The overwhelming majority of places already did this, but a small
handful of places had a hyphen.
Yugo Nagata.
Discussion:
https://postgr.es/m/CAEZATCXnnuORE2BoGwHw2zbtVvsPOLhbfVmEk9GxRzK%2Bx3OW-Q%40mail.gmail.com
Branch
--
master
Details
-
security barrier views or tables with row-level
security policies.
Yugo Nagata, reviewed by Erik Wienhold and Dean Rasheed.
Discussion:
https://postgr.es/m/20240701220817.483f9b645b95611f8b1f65da%40sranhm.sraoss.co.jp
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff
quote_identifier() in the deparsing code.
Back-patch to all supported versions.
Dean Rasheed, reviewed by Tom Lane.
Discussion:
https://postgr.es/m/CAEZATCXTpAS%3DncfLNTZ7YS6O5puHeLg_SUYAit%2Bcs7wsrd9Msg%40mail.gmail.com
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff
using quote_identifier() in the deparsing code.
This oversight was limited to the SQL/JSON query functions
JSON_EXISTS(), JSON_QUERY(), and JSON_VALUE().
Back-patch to v17, where these functions were added.
Dean Rasheed, reviewed by Tom Lane.
Discussion:
https://postgr.es/m/CAEZATCXTpAS
using quote_identifier() in the deparsing code.
This oversight was limited to the SQL/JSON query functions
JSON_EXISTS(), JSON_QUERY(), and JSON_VALUE().
Back-patch to v17, where these functions were added.
Dean Rasheed, reviewed by Tom Lane.
Discussion:
https://postgr.es/m/CAEZATCXTpAS
quote_identifier() in the deparsing code.
Back-patch to all supported versions.
Dean Rasheed, reviewed by Tom Lane.
Discussion:
https://postgr.es/m/CAEZATCXTpAS%3DncfLNTZ7YS6O5puHeLg_SUYAit%2Bcs7wsrd9Msg%40mail.gmail.com
Branch
--
REL_16_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff
quote_identifier() in the deparsing code.
Back-patch to all supported versions.
Dean Rasheed, reviewed by Tom Lane.
Discussion:
https://postgr.es/m/CAEZATCXTpAS%3DncfLNTZ7YS6O5puHeLg_SUYAit%2Bcs7wsrd9Msg%40mail.gmail.com
Branch
--
REL_15_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff
quote_identifier() in the deparsing code.
Back-patch to all supported versions.
Dean Rasheed, reviewed by Tom Lane.
Discussion:
https://postgr.es/m/CAEZATCXTpAS%3DncfLNTZ7YS6O5puHeLg_SUYAit%2Bcs7wsrd9Msg%40mail.gmail.com
Branch
--
REL_13_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff
quote_identifier() in the deparsing code.
Back-patch to all supported versions.
Dean Rasheed, reviewed by Tom Lane.
Discussion:
https://postgr.es/m/CAEZATCXTpAS%3DncfLNTZ7YS6O5puHeLg_SUYAit%2Bcs7wsrd9Msg%40mail.gmail.com
Branch
--
REL_14_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff
quote_identifier() in the deparsing code.
Back-patch to all supported versions.
Dean Rasheed, reviewed by Tom Lane.
Discussion:
https://postgr.es/m/CAEZATCXTpAS%3DncfLNTZ7YS6O5puHeLg_SUYAit%2Bcs7wsrd9Msg%40mail.gmail.com
Branch
--
REL_17_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff
Fix #include order in timestamp.c.
Oversight in 036bdcec9f.
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/33152358453cc46f986483e9f82418fb8ba8eaef
Modified Files
--
src/backend/utils/adt/timestamp.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Add a planner support function for numeric generate_series().
This allows the planner to estimate the number of rows returned by
generate_series(numeric, numeric[, numeric]), when the input values
can be estimated at plan time.
Song Jinzhou, reviewed by Dean Rasheed and David Rowley.
Discussion
quot;exact" is true, and up to 2 or 3 times as fast as the old
div_var_fast() function when "exact" is false.
Dean Rasheed, reviewed by Joel Jacobson.
Discussion:
https://postgr.es/m/caezatcvhr10bpdjsanh0u2+sg6ato3md0g+cjkdnrmd-c8h...@mail.gmail.com
Branch
--
master
Details
---
h
Fix wrong varnullingrels error for MERGE WHEN NOT MATCHED BY SOURCE.
If a MERGE command contains WHEN NOT MATCHED BY SOURCE actions, the
source relation appears on the outer side of the join. Thus, any Vars
referring to the source in the merge join condition, actions, and
RETURNING list should be
Fix wrong varnullingrels error for MERGE WHEN NOT MATCHED BY SOURCE.
If a MERGE command contains WHEN NOT MATCHED BY SOURCE actions, the
source relation appears on the outer side of the join. Thus, any Vars
referring to the source in the merge join condition, actions, and
RETURNING list should be
Fix incorrect non-strict join recheck in MERGE WHEN NOT MATCHED BY SOURCE.
If a MERGE command contains WHEN NOT MATCHED BY SOURCE actions, the
merge join condition is used by the executor to distinguish MATCHED
from NOT MATCHED BY SOURCE cases. However, this qual is executed using
the output from
Fix incorrect non-strict join recheck in MERGE WHEN NOT MATCHED BY SOURCE.
If a MERGE command contains WHEN NOT MATCHED BY SOURCE actions, the
merge join condition is used by the executor to distinguish MATCHED
from NOT MATCHED BY SOURCE cases. However, this qual is executed using
the output from
Fix compiler warning in mul_var_short().
Some compilers (e.g., gcc before version 7) mistakenly think "carry"
might be used uninitialized.
Reported by Tom Lane, per various buildfarm members, e.g. arowana.
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/7cac6307a43
be a noticeable slowdown
on 32-bit machines. That seems to be an acceptable tradeoff, given the
performance gains for other inputs, and the effort that would be
required to maintain code specifically targeting 32-bit machines.
Joel Jacobson and Dean Rasheed.
Discussion:
https://postgr.es/m
a bit using macros
and exploiting the fact that some portions of the code are shared
between the different cases.
Dean Rasheed, reviewed by Joel Jacobson.
Discussion:
https://postgr.es/m/9d8a4a42-c354-41f3-bbf3-199e1957db97%40app.fastmail.com
Branch
--
master
Details
---
https
y quotient digits after the decimal point.
In addition, it is not necessary to have separate code to handle
reversed bounds, since the signs cancel out when dividing.
As with b0e9e4d76c and a2a0c7c29e, no back-patch.
Dean Rasheed, reviewed by Joel Jacobson.
Discussion:
https://postgr.es/m/C
larger
numbers of digits in the shorter input.
Joel Jacobson and Dean Rasheed.
Discussion:
https://postgr.es/m/44d2ffca-d560-4919-b85a-4d0706094...@app.fastmail.com
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/ca481d3c9ab7bf69ff0c8d71ad3951d407f6a33c
Modified
(1000).
Back-patch to all supported branches.
Dean Rasheed, reviewed by Joel Jacobson.
Discussion:
https://postgr.es/m/CAEZATCXB%2BrDTuMjhK5ZxcouufigSc-X4tGJCBTMpZ3n%3DxxQuhg%40mail.gmail.com
Branch
--
REL_16_STABLE
Details
---
https://git.postgresql.org/pg/commi
(1000).
Back-patch to all supported branches.
Dean Rasheed, reviewed by Joel Jacobson.
Discussion:
https://postgr.es/m/CAEZATCXB%2BrDTuMjhK5ZxcouufigSc-X4tGJCBTMpZ3n%3DxxQuhg%40mail.gmail.com
Branch
--
REL_13_STABLE
Details
---
https://git.postgresql.org/pg/commi
(1000).
Back-patch to all supported branches.
Dean Rasheed, reviewed by Joel Jacobson.
Discussion:
https://postgr.es/m/CAEZATCXB%2BrDTuMjhK5ZxcouufigSc-X4tGJCBTMpZ3n%3DxxQuhg%40mail.gmail.com
Branch
--
REL_15_STABLE
Details
---
https://git.postgresql.org/pg/commi
(1000).
Back-patch to all supported branches.
Dean Rasheed, reviewed by Joel Jacobson.
Discussion:
https://postgr.es/m/CAEZATCXB%2BrDTuMjhK5ZxcouufigSc-X4tGJCBTMpZ3n%3DxxQuhg%40mail.gmail.com
Branch
--
REL_12_STABLE
Details
---
https://git.postgresql.org/pg/commi
(1000).
Back-patch to all supported branches.
Dean Rasheed, reviewed by Joel Jacobson.
Discussion:
https://postgr.es/m/CAEZATCXB%2BrDTuMjhK5ZxcouufigSc-X4tGJCBTMpZ3n%3DxxQuhg%40mail.gmail.com
Branch
--
master
Details
---
https://git.postgresql.org/pg/commi
(1000).
Back-patch to all supported branches.
Dean Rasheed, reviewed by Joel Jacobson.
Discussion:
https://postgr.es/m/CAEZATCXB%2BrDTuMjhK5ZxcouufigSc-X4tGJCBTMpZ3n%3DxxQuhg%40mail.gmail.com
Branch
--
REL_14_STABLE
Details
---
https://git.postgresql.org/pg/commi
(1000).
Back-patch to all supported branches.
Dean Rasheed, reviewed by Joel Jacobson.
Discussion:
https://postgr.es/m/CAEZATCXB%2BrDTuMjhK5ZxcouufigSc-X4tGJCBTMpZ3n%3DxxQuhg%40mail.gmail.com
Branch
--
REL_17_STABLE
Details
---
https://git.postgresql.org/pg/commi
doc: Mention all options equivalent to pg_dump --filter patterns.
In the documentation for pg_dump's new --filter option, added by
commit a5cf808be5, each object pattern should match some other
existing pg_dump option, but some had been omitted, so add them.
Noted by Daniel Gustafsson, reviewed b
Fix PL/pgSQL's handling of integer ranges containing underscores.
Commit faff8f8e47 allowed integer literals to contain underscores, but
failed to update the lexer's "numericfail" rule. As a result, a
decimal integer literal containing underscores would fail to parse, if
used in an integer range w
Fix PL/pgSQL's handling of integer ranges containing underscores.
Commit faff8f8e47 allowed integer literals to contain underscores, but
failed to update the lexer's "numericfail" rule. As a result, a
decimal integer literal containing underscores would fail to parse, if
used in an integer range w
Fix another couple of outdated comments for MERGE RETURNING.
Oversights in c649fa24a4 which added RETURNING support to MERGE.
Discussion:
https://postgr.es/m/caaphdvpqp6vtuzg-_josueibgyqnrnvxj-vdf+hjlxjhdhz...@mail.gmail.com
Branch
--
master
Details
---
https://git.postgresql.org/pg/co
Use macro NUM_MERGE_MATCH_KINDS instead of '3' in MERGE code.
Code quality improvement for 0294df2f1f84.
Aleksander Alekseev, reviewed by Richard Guo.
Discussion:
https://postgr.es/m/CAJ7c6TMsiaV5urU_Pq6zJ2tXPDwk69-NKVh4AMN5XrRiM7N%2BGA%40mail.gmail.com
Branch
--
master
Details
---
ht
TARGET is
equivalent to writing WHEN NOT MATCHED BY TARGET.
Dean Rasheed, reviewed by Alvaro Herrera, Ted Yu and Vik Fearing.
Discussion:
https://postgr.es/m/CAEZATCWqnKGc57Y_JanUBHQXNKcXd7r=0r4nezuvwp+syrk...@mail.gmail.com
Branch
--
master
Details
---
https://git.postgresql.org/pg
file.
The existing random(), random_normal(), and setseed() functions are
moved there too, so that they can all share the same PRNG state, which
is kept private to that file.
Dean Rasheed, reviewed by Jian He, David Zhang, Aleksander Alekseev,
and Tomas Vondra.
Discussion:
https://postgr.es
Add "--exclude-extension" to pg_dump's options.
This option (or equivalently specifying "exclude extension pattern" in
a filter file) allows extensions matching the specified pattern to be
excluded from the dump.
Ayush Vatsa, reviewed by Junwang Zhao, Dean Rashe
Fix PDF doc generation.
Commit c649fa24a4 broke PDF generation, due to a misplaced id
attribute.
Per buildfarm member crake.
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/7eb9a8201890f3b208fd4c109a5b08bf139b692a
Modified Files
--
doc/src/sgml/func.sg
ror to use it anywhere outside of a MERGE
query's RETURNING list.
Dean Rasheed, reviewed by Isaac Morland, Vik Fearing, Alvaro Herrera,
Gurjeet Singh, Jian He, Jeff Davis, Merlin Moncure, Peter Eisentraut,
and Wolfgang Walther.
Discussion:
http://postgr.es/m/CAEZATCWePEGQR5LBn-vD6SfeLZafzE
Fix EXPLAIN output for subplans in MERGE.
Given a subplan in a MERGE query, EXPLAIN would sometimes fail to
properly display expressions involving Params referencing variables in
other parts of the plan tree.
This would affect subplans outside the topmost join plan node, for
which expansion of Pa
Fix EXPLAIN output for subplans in MERGE.
Given a subplan in a MERGE query, EXPLAIN would sometimes fail to
properly display expressions involving Params referencing variables in
other parts of the plan tree.
This would affect subplans outside the topmost join plan node, for
which expansion of Pa
1 - 100 of 338 matches
Mail list logo