jit: Add support for LLVM 12.
LLVM 12, to be released in a few months, made some breaking changes to
the Orc JIT interface. OrcV2 eventually will make it easier to support
features like concurrent JIT compilation, but this commit only allows
to compile against LLVM 12.
This commit is a bit bigger
Andrew Dunstan writes:
> On 11/9/20 5:15 PM, Tom Lane wrote:
>> Hm. To fix it this way, we'd have to push the test-script change
>> into the pre-9.5 branches. There's no technical reason we can't do
>> that, I don't think, though it's a bit outside our normal practices.
> I doubt it's necessary
On 11/9/20 5:15 PM, Tom Lane wrote:
> Andrew Dunstan writes:
>> On 11/9/20 4:29 PM, Tom Lane wrote:
>>> I think probably the right fix is just to change that test case to
>>> use a different implementation function, per [1]. I'm holding off
>>> pushing the fix till after this week's wraps, thou
Stamp 9.5.24.
Branch
--
REL9_5_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/f57cc8693b15b79186684f02b729090a149b7555
Modified Files
--
configure| 18 +-
configure.in | 2 +-
doc/bug.template
Stamp 9.6.20.
Branch
--
REL9_6_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/e4554425e6d3b429a207ac1a109af9d7e1d14da6
Modified Files
--
configure| 18 +-
configure.in | 2 +-
doc/bug.template
Stamp 10.15.
Branch
--
REL_10_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/e6c792ab72b99a3d68bf0696d0720e9afc61695c
Modified Files
--
configure| 18 +-
configure.in | 2 +-
doc/bug.template
Stamp 11.10.
Branch
--
REL_11_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/7e0c8283c021abf15f24f217e6bcc7faf4860b34
Modified Files
--
configure| 18 +-
configure.in | 2 +-
doc/bug.template
Stamp 12.5.
Branch
--
REL_12_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/6bb1b38fa5388a4aa39ed9e56ef477f618fb28e1
Modified Files
--
configure| 18 +-
configure.in | 2 +-
src/include/pg_config.h.win32
Stamp 13.1.
Branch
--
REL_13_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/6daf725a9c66e880fd76d25279ce00710535e030
Modified Files
--
configure| 18 +-
configure.in | 2 +-
2 files changed, 10 insertions(+), 10 deletions(-)
Andrew Dunstan writes:
> On 11/9/20 4:29 PM, Tom Lane wrote:
>> I think probably the right fix is just to change that test case to
>> use a different implementation function, per [1]. I'm holding off
>> pushing the fix till after this week's wraps, though.
> I'd be ok with that. Can we devise a
On 11/9/20 4:29 PM, Tom Lane wrote:
> Andrew Dunstan writes:
>> On 11/4/20 4:10 PM, Tom Lane wrote:
>>> Declare assorted array functions using anycompatible not anyelement.
>> This patch broke cross-version pg_upgrade testing.
> Uh, yeah ... didn't you get my two prior messages about that?
Ye
Andrew Dunstan writes:
> On 11/4/20 4:10 PM, Tom Lane wrote:
>> Declare assorted array functions using anycompatible not anyelement.
> This patch broke cross-version pg_upgrade testing.
Uh, yeah ... didn't you get my two prior messages about that?
> I have cured crake
> for the moment by having
On 11/4/20 4:10 PM, Tom Lane wrote:
> Declare assorted array functions using anycompatible not anyelement.
>
> Convert array_append, array_prepend, array_cat, array_position,
> array_positions, array_remove, array_replace, and width_bucket
> to use anycompatiblearray. This is a simple extension
Doc: clarify data type behavior of COALESCE and NULLIF.
After studying the code, NULLIF is a lot more subtle than you might
have guessed.
Discussion:
https://postgr.es/m/[email protected]
Branch
--
REL_11_STABLE
Details
---
https://git.post
Doc: clarify data type behavior of COALESCE and NULLIF.
After studying the code, NULLIF is a lot more subtle than you might
have guessed.
Discussion:
https://postgr.es/m/[email protected]
Branch
--
REL9_5_STABLE
Details
---
https://git.post
Doc: clarify data type behavior of COALESCE and NULLIF.
After studying the code, NULLIF is a lot more subtle than you might
have guessed.
Discussion:
https://postgr.es/m/[email protected]
Branch
--
master
Details
---
https://git.postgresql.
Doc: clarify data type behavior of COALESCE and NULLIF.
After studying the code, NULLIF is a lot more subtle than you might
have guessed.
Discussion:
https://postgr.es/m/[email protected]
Branch
--
REL_10_STABLE
Details
---
https://git.post
Doc: clarify data type behavior of COALESCE and NULLIF.
After studying the code, NULLIF is a lot more subtle than you might
have guessed.
Discussion:
https://postgr.es/m/[email protected]
Branch
--
REL_12_STABLE
Details
---
https://git.post
Doc: clarify data type behavior of COALESCE and NULLIF.
After studying the code, NULLIF is a lot more subtle than you might
have guessed.
Discussion:
https://postgr.es/m/[email protected]
Branch
--
REL_13_STABLE
Details
---
https://git.post
Doc: clarify data type behavior of COALESCE and NULLIF.
After studying the code, NULLIF is a lot more subtle than you might
have guessed.
Discussion:
https://postgr.es/m/[email protected]
Branch
--
REL9_6_STABLE
Details
---
https://git.post
Remove ineffective heapam CHECK_FOR_INTERRUPTS().
Remove a CHECK_FOR_INTERRUPTS() call that could never actually handle an
interrupt. We always have a heap page buffer lock at this point.
Having a useless CHECK_FOR_INTERRUPTS() call is harmless but misleading.
It is probably possible to work aro
Translation updates
Source-Git-URL: https://git.postgresql.org/git/pgtranslation/messages.git
Source-Git-Hash: 4bbd5d22a42690d7e76c41ae04044d8d9ef2d5ed
Branch
--
REL_11_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/5a55a80cc35da1e450f8d0fe22aa380e7fe68d64
Modified Files
--
Translation updates
Source-Git-URL: https://git.postgresql.org/git/pgtranslation/messages.git
Source-Git-Hash: 2ffedf5ea37677f39cdc1eb92a1e78762cd3fb0e
Branch
--
REL_13_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/62e7ae75f441e7c91f446b05f5b206fe01e34f0c
Modified Files
--
Translation updates
Source-Git-URL: https://git.postgresql.org/git/pgtranslation/messages.git
Source-Git-Hash: 73696049f4e22e6bffd9cf13fdd816b7dd5b6fd8
Branch
--
REL_10_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/d7d9dc144075c8d4b37c38397709d178db14d0c0
Modified Files
--
Translation updates
Source-Git-URL: https://git.postgresql.org/git/pgtranslation/messages.git
Source-Git-Hash: f09d69720b2d48f37d3b555c38501b6529c0c6ac
Branch
--
REL9_6_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/d8a9722bd39c4eced4b13551f0401b37ff72ef74
Modified Files
--
Translation updates
Source-Git-URL: https://git.postgresql.org/git/pgtranslation/messages.git
Source-Git-Hash: 8740d75e31771525e9bb55e71bfd343faae253b4
Branch
--
REL9_5_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/7a581f390165fd61f5bb7e6edba97a69991e61e7
Modified Files
--
Translation updates
Source-Git-URL: https://git.postgresql.org/git/pgtranslation/messages.git
Source-Git-Hash: 3bbbf347254dd914c5ae4b5d0bba9a1ddc28eaa0
Branch
--
REL_12_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/a98b46194434927b8402b08ac0edfa6408c7e823
Modified Files
--
Remove analyze_new_cluster script from pg_upgrade
Since this script just runs vacuumdb anyway, remove the script and
replace the instructions to run it with instructions to run vacuumdb
directly.
Reviewed-By: Michael Paquier
Discussion:
https://postgr.es/m/CABUevEwg5LDFzthhxzSj7sZGMiVsZe0VVNbzzw
Remove incorrect %s in string
Appears to have been a copy/paste error in the original commit that
moved the messages to fe_utils/.
Author: Tang, Haiying
Backpatch-through: 13
Discussion:
https://postgr.es/m/3321cbcea76d4d2c8320a05c19b9304a@G08CNEXMBPEKD05.g08.fujitsu.local
Branch
--
master
Remove incorrect %s in string
Appears to have been a copy/paste error in the original commit that
moved the messages to fe_utils/.
Author: Tang, Haiying
Backpatch-through: 13
Discussion:
https://postgr.es/m/3321cbcea76d4d2c8320a05c19b9304a@G08CNEXMBPEKD05.g08.fujitsu.local
Branch
--
REL_13
30 matches
Mail list logo
