Add file containing extensions of the LLVM C API.
Author: Andres Freund
Discussion:
https://postgr.es/m/20170901064131.tazjxwus3k2w3...@alap3.anarazel.de
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/31bc604e0b74805ff9e84a2d549ca82be665d0a6
Modified Files
--
Empty CXXFLAGS inherited from autoconf.
We do the same for CFLAGS. This was an omission in 6869b4f25.
Reported-By: Catalin Iacob
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/a02671cfdeac3bb86ebf8f8577faf69730c4f80e
Modified Files
--
configure|
Basic JIT provider and error handling infrastructure.
This commit introduces:
1) JIT provider abstraction, which allows JIT functionality to be
implemented in separate shared libraries. That's desirable because
it allows to install JIT support as a separate package, and because
it allows
Fix typo in BITCODE_CXXFLAGS assignment.
Typoed-In: 5b2526c83832e
Reported-By: Catalin Iacob
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/4317cc68a284f041abc583ced4ef7ede2f73fb51
Modified Files
--
configure| 2 +-
configure.in | 2 +-
2 files chang
Prevent extensions from creating custom GUCs that are GUC_LIST_QUOTE.
Pending some solution for the problems noted in commit 742869946,
disallow dynamic creation of GUC_LIST_QUOTE variables.
If there are any extensions out there using this feature, they'd not
be happy for us to start enforcing th
Fix mishandling of quoted-list GUC values in pg_dump and ruleutils.c.
Code that prints out the contents of setconfig or proconfig arrays in
SQL format needs to handle GUC_LIST_QUOTE variables differently from
other ones, because for those variables, flatten_set_variable_args()
already applied a la
Fix mishandling of quoted-list GUC values in pg_dump and ruleutils.c.
Code that prints out the contents of setconfig or proconfig arrays in
SQL format needs to handle GUC_LIST_QUOTE variables differently from
other ones, because for those variables, flatten_set_variable_args()
already applied a la
Fix mishandling of quoted-list GUC values in pg_dump and ruleutils.c.
Code that prints out the contents of setconfig or proconfig arrays in
SQL format needs to handle GUC_LIST_QUOTE variables differently from
other ones, because for those variables, flatten_set_variable_args()
already applied a la
Fix mishandling of quoted-list GUC values in pg_dump and ruleutils.c.
Code that prints out the contents of setconfig or proconfig arrays in
SQL format needs to handle GUC_LIST_QUOTE variables differently from
other ones, because for those variables, flatten_set_variable_args()
already applied a la
Fix mishandling of quoted-list GUC values in pg_dump and ruleutils.c.
Code that prints out the contents of setconfig or proconfig arrays in
SQL format needs to handle GUC_LIST_QUOTE variables differently from
other ones, because for those variables, flatten_set_variable_args()
already applied a la
Fix mishandling of quoted-list GUC values in pg_dump and ruleutils.c.
Code that prints out the contents of setconfig or proconfig arrays in
SQL format needs to handle GUC_LIST_QUOTE variables differently from
other ones, because for those variables, flatten_set_variable_args()
already applied a la
Improve predtest.c's handling of cases with NULL-constant inputs.
Currently, if operator_predicate_proof() is given an operator clause like
"something op NULL", it just throws up its hands and reports it can't prove
anything. But we can often do better than that, if the operator is strict,
becaus
Change oddly-chosen OID allocation.
I noticed while fooling with John Naylor's bootstrap-data patch that we had
one high-numbered manually assigned OID, , which evidently came from a
submission that the committer didn't bother to bring into line with usual
OID allocation practices before commi
pg_controldata: Prevent division-by-zero errors
If the control file is corrupted and specifies the WAL segment size
to be 0 bytes, calculating the latest checkpoint's REDO WAL file
will fail with a division-by-zero error. Show it as "???" instead.
Also reword the warning message a bit and send i
Fix relcache handling of the 'default' partition
My commit 4dba331cb3dc that moved around CommandCounterIncrement calls
in partitioning DDL code unearthed a problem with the relcache handling
for the 'default' partition: the construction of a correct relcache
entry for the partitioned table was at
Add general purpose hasing functions to pgbench.
Hashing function is useful for simulating real-world workload in test like
WEB workload, as an example - YCSB benchmarks.
Author: Ildar Musin with minor editorization by me
Reviewed by: Fabien Coelho, me
Discussion:
https://www.postgresql.org/mess
Fix typo.
Patch by me.
Branch
--
REL9_5_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/487a6e38de9048f29a1c23cb2c796cce3b1cdd62
Modified Files
--
doc/src/sgml/protocol.sgml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Fix typo.
Patch by me.
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/8bb3c7d347f0c74aa12beeef3599984021323e7d
Modified Files
--
doc/src/sgml/protocol.sgml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Fix typo.
Patch by me.
Branch
--
REL9_3_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/9bf3458a957a54dd76c339aad446a3aaaf85699f
Modified Files
--
doc/src/sgml/protocol.sgml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Fix typo.
Patch by me.
Branch
--
REL9_6_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/36e1d45718c3415d42a12faddf4d6b2f0c488f2b
Modified Files
--
doc/src/sgml/protocol.sgml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Fix typo.
Patch by me.
Branch
--
REL_10_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/31c869ef1a7cb4cdcda858ae860b9704b23befd9
Modified Files
--
doc/src/sgml/protocol.sgml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Fix typo.
Patch by me.
Branch
--
REL9_4_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/9312fcf03b4889f9f2ba1c9b4a3447951a5bb6fb
Modified Files
--
doc/src/sgml/protocol.sgml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Handle heap rewrites even better in logical decoding
Logical decoding should not publish anything about tables created as
part of a heap rewrite during DDL. Those tables don't exist externally,
so consumers of logical decoding cannot do anything sensible with that
information. In ab28feae2bd3d46
Add strict_word_similarity to pg_trgm module
strict_word_similarity is similar to existing word_similarity function but
it takes into account word boundaries to compute similarity.
Author: Alexander Korotkov
Review by: David Steele, Liudmila Mantrova, me
Discussion:
https://www.postgresql.org/me
Add configure tests for stdbool.h and sizeof bool
This will allow us to assess how many platforms have bool with a size
other than 1, which will help us decide how to go forward with using
stdbool.h.
Discussion:
https://www.postgresql.org/message-id/flat/3a0fe7e1-5ed1-414b-9230-53bbc0ed1...@2ndq
Repair crash with unsortable grouping sets.
If there were multiple grouping sets, none of them empty, all of which
were unsortable, then an oversight in consider_groupingsets_paths led
to a null pointer dereference. Fix, and add a regression test for this
case.
Per report from Dang Minh Huong, th
Repair crash with unsortable grouping sets.
If there were multiple grouping sets, none of them empty, all of which
were unsortable, then an oversight in consider_groupingsets_paths led
to a null pointer dereference. Fix, and add a regression test for this
case.
Per report from Dang Minh Huong, th
Rework word_similarity documentation, make it close to actual algorithm.
word_similarity before claimed as returning similarity of closest word in
string, but, actually it returns similarity of substring. Also fix mistyped
comments.
Author: Alexander Korotkov
Review by: David Steele, Liudmila Man
Rework word_similarity documentation, make it close to actual algorithm.
word_similarity before claimed as returning similarity of closest word in
string, but, actually it returns similarity of substring. Also fix mistyped
comments.
Author: Alexander Korotkov
Review by: David Steele, Liudmila Man
Rework word_similarity documentation, make it close to actual algorithm.
word_similarity before claimed as returning similarity of closest word in
string, but, actually it returns similarity of substring. Also fix mistyped
comments.
Author: Alexander Korotkov
Review by: David Steele, Liudmila Man
doc: Small wording improvement
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/d652e3525b8ff988db717ed66c467b6fd78a32bc
Modified Files
--
doc/src/sgml/config.sgml | 8
1 file changed, 4 insertions(+), 4 deletions(-)
31 matches
Mail list logo