Based on the infrastructure added in b8d7f053c5c2b, this allows
expressions in expensive queries to be compiled to native code. In
TPC-H this yields up to 40% of speedups.
Whenever a query has a total cost over jit_expression_minimum, all
expressions in it will be JIT compiled. That allows to pe
On Sat, Apr 1, 2017 at 8:41 PM, Andres Freund wrote:
> For the upcoming JIT support LLVM is required. To avoid issues with
> having to support multiple LLVM versions, add a vendored version of
> LLVM.
>
> The large size of LLVM makes this not great, but I think it's better
> than the alternatives
Re: Kevin Grittner 2017-04-01
> Try to fix breakage of sepgsql hooks by ENR patch.
>
> Turned up by buildfarm animal rhinoceros. Fixing blind. Will have
> to wait for next run by rhinoceros to know whether it worked.
Fwiw, I was seeing sepgsql problems on Ubuntu xenial and trusty this
morning
On Sat, Apr 1, 2017 at 5:27 PM, Thomas Munro
wrote:
> On Sat, Apr 1, 2017 at 8:41 PM, Andres Freund wrote:
>> For the upcoming JIT support LLVM is required. To avoid issues with
>> having to support multiple LLVM versions, add a vendored version of
>> LLVM.
>>
>> The large size of LLVM makes thi
On Sat, Apr 1, 2017 at 3:41 AM, Andres Freund wrote:
> For the upcoming JIT support LLVM is required. To avoid issues with
> having to support multiple LLVM versions, add a vendored version of
> LLVM.
>
> The large size of LLVM makes this not great, but I think it's better
> than the alternatives
On 1 April 2017 at 08:41, Andres Freund wrote:
> Originally slated for v11, discussions at pgconf.us convinced me to
> add this to v10.
+1
--
Simon Riggshttp://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
--
Sent via pgsql-commit
Write "waiting for checkpoint" on regular progress row
When reporting progress, make the "waiting for checkpoint" test be
overwritten by the file-based progress once it's completed. This is more
consistent with how we report the rest of the progress.
Suggested by Jeff Janes
Branch
--
master
Back-patch checkpoint clarification docs and pg_basebackup updates
This backpatches 51e26c9 and 7220c7b, including both documentation
updates clarifying the checkpoints at the beginning of base backups and
the messages in verbose and progress mdoe of pg_basebackup.
Author: Michael Banck
Discussio
Back-patch checkpoint clarification docs and pg_basebackup updates
This backpatches 51e26c9 and 7220c7b, including both documentation
updates clarifying the checkpoints at the beginning of base backups and
the messages in verbose and progress mdoe of pg_basebackup.
Author: Michael Banck
Discussio
Back-patch checkpoint clarification docs and pg_basebackup updates
This backpatches 51e26c9 and 7220c7b, including both documentation
updates clarifying the checkpoints at the beginning of base backups and
the messages in verbose and progress mdoe of pg_basebackup.
Author: Michael Banck
Discussio
BRIN auto-summarization
Previously, only VACUUM would cause a page range to get initially
summarized by BRIN indexes, which for some use cases takes too much time
since the inserts occur. To avoid the delay, have brininsert request a
summarization run for the previous range as soon as the first t
On 2017-04-01 10:21:27 -0400, Robert Haas wrote:
> On Sat, Apr 1, 2017 at 3:41 AM, Andres Freund wrote:
> > For the upcoming JIT support LLVM is required. To avoid issues with
> > having to support multiple LLVM versions, add a vendored version of
> > LLVM.
> >
> > The large size of LLVM makes th
Fix expected output
Previous commit had a thinko in the expected output for new tests.
Per buildfarm
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/3a82129a40a3a2987356d4051e017fd456876c8d
Modified Files
--
src/test/regress/expected/brin.out | 2 +-
1 f
On 2017-04-01 21:27:42 +1300, Thomas Munro wrote:
> On Sat, Apr 1, 2017 at 8:41 PM, Andres Freund wrote:
> > For the upcoming JIT support LLVM is required. To avoid issues with
> > having to support multiple LLVM versions, add a vendored version of
> > LLVM.
> >
> > The large size of LLVM makes t
BRIN de-summarization
When the BRIN summary tuple for a page range becomes too "wide" for the
values actually stored in the table (because the tuples that were
present originally are no longer present due to updates or deletes), it
can be useful to remove the outdated summary tuple, so that a futu
On 03/31/2017 02:38 PM, Tom Lane wrote:
> Andrew Dunstan writes:
>> Full Text Search support for json and jsonb
>> The new functions are ts_headline() and to_tsvector.
> Should this not have included a catversion bump?
>
>
Oops, you're right. I see there have been severa
Fix two undocumented parameters to functions from ENR patch.
On ProcessUtility document the parameter, to match others.
On CreateCachedPlan drop the queryEnv parameter. It was not
referenced within the function, and had been added on the
assumption that with some unknown future usage of QueryEnv
On Saturday, April 1, 2017 3:01:18 PM EDT Andres Freund wrote:
> On 2017-04-01 10:21:27 -0400, Robert Haas wrote:
> > On Sat, Apr 1, 2017 at 3:41 AM, Andres Freund wrote:
> > > For the upcoming JIT support LLVM is required. To avoid issues with
> > > having to support multiple LLVM versions, add
Allow psql variable substitution to occur in backtick command strings.
Previously, text between backquotes in a psql metacommand's arguments
was always passed to the shell literally. That considerably hobbles
the usefulness of the feature for scripting, so we'd foreseen for a long
time that we'd
On Sat, Apr 1, 2017 at 10:32 PM, Alvaro Herrera wrote:
> BRIN auto-summarization
>
>
> Most of the new code here is in autovacuum, which can now be told about
> "work items" to process.
>
Nice framework!
> This can be used for other things such as GIN
> pending list cleaning, perhaps visibility
20 matches
Mail list logo
