On Tue, Nov 29, 2022 at 4:07 PM David Rowley wrote:
> On Wed, 30 Nov 2022 at 03:31, Tom Lane wrote:
> >
> > Alvaro Herrera writes:
> > > IMO it was a mistake to turn JIT on in the default config, so that's
> one
> > > thing you'll likely want to change.
> >
> > I wouldn't necessarily go quite
On 2022-11-30 We 11:36, Tom Lane wrote:
> Andres Freund writes:
>> On November 30, 2022 3:47:32 AM PST, Andrew Dunstan
>> wrote:
>>> I think Alvaro's point is that it would have been better to work out
>>> these wrinkles before turning on JIT by default. Based on anecdotal
>>> reports from
Andres Freund writes:
> On November 30, 2022 3:47:32 AM PST, Andrew Dunstan
> wrote:
>> I think Alvaro's point is that it would have been better to work out
>> these wrinkles before turning on JIT by default. Based on anecdotal
>> reports from the field I'm inclined to agree.
> The problem is
Hi,
On November 30, 2022 3:47:32 AM PST, Andrew Dunstan wrote:
>
>On 2022-11-29 Tu 16:06, David Rowley wrote:
>> On Wed, 30 Nov 2022 at 03:31, Tom Lane wrote:
>>> Alvaro Herrera writes:
IMO it was a mistake to turn JIT on in the default config, so that's one
thing you'll likely want
On 2022-11-29 Tu 16:06, David Rowley wrote:
> On Wed, 30 Nov 2022 at 03:31, Tom Lane wrote:
>> Alvaro Herrera writes:
>>> IMO it was a mistake to turn JIT on in the default config, so that's one
>>> thing you'll likely want to change.
>> I wouldn't necessarily go quite that far, but I do think
On Tue, 2022-11-29 at 19:09 +0100, Alvaro Herrera wrote:
> On 2022-Nov-29, Mladen Gogala wrote:
>
> > Hmmm, I think I will run pgbench with and without JIT on and see
> > the
> > difference.
>
> I doubt you'll notice anything, because the pgbench queries will be
> far
> below the JIT cost, so
On Wed, 30 Nov 2022 at 03:31, Tom Lane wrote:
>
> Alvaro Herrera writes:
> > IMO it was a mistake to turn JIT on in the default config, so that's one
> > thing you'll likely want to change.
>
> I wouldn't necessarily go quite that far, but I do think that the
> default cost thresholds for
On 2022-Nov-29, Mladen Gogala wrote:
> Hmmm, I think I will run pgbench with and without JIT on and see the
> difference.
I doubt you'll notice anything, because the pgbench queries will be far
below the JIT cost, so nothing will get JIT compiled at all. Or are you
planning on using a custom
Alvaro Herrera writes:
> IMO it was a mistake to turn JIT on in the default config, so that's one
> thing you'll likely want to change.
I wouldn't necessarily go quite that far, but I do think that the
default cost thresholds for invoking it are enormously too low,
or else there are serious bugs
On 11/29/22 03:36, Alvaro Herrera wrote:
On 2022-Nov-28, Mladen Gogala wrote:
As for JIT, I've recently asked that question myself. I was told that
PostgreSQL with LLVM enabled performs approximately 25% better than without
it.
Hmm, actually, normally you're better off turning JIT off,
On 11/29/22 03:31, Alvaro Herrera wrote:
On 2022-Nov-28, Mladen Gogala wrote:
You'll probably be glad to learn that we have hints now.
What hints are you talking about? As I understand, we still don't have
Oracle-style query hints.
https://github.com/ossc-db/pg_hint_plan
--
Mladen Gogala
On 2022-Nov-28, Mladen Gogala wrote:
> As for JIT, I've recently asked that question myself. I was told that
> PostgreSQL with LLVM enabled performs approximately 25% better than without
> it.
Hmm, actually, normally you're better off turning JIT off, because it's
very common to diagnose cases
On 2022-Nov-28, Mladen Gogala wrote:
> You'll probably be glad to learn that we have hints now.
What hints are you talking about? As I understand, we still don't have
Oracle-style query hints.
--
Álvaro HerreraBreisgau, Deutschland — https://www.EnterpriseDB.com/
On 11/28/22 19:34, Justin Pryzby wrote:
In addition to setting work_mem, you can also (since v13) set
hash_mem_multiplier.
Is there any guidance on setting this? Or is it still "use the default
unless you can play around with it"?
default_toast_compression = lz4 # v14
On 11/28/22 21:59, Josh Berkus wrote:
Hey, folks:
I haven't configured a PostgreSQL server since version 11 (before
that, I did quite a few).
What's changed in terms of performance configuration since then? Have
the fundamentals of shared_buffers/work_mem/max_connections changed at
all?
On Mon, Nov 28, 2022 at 06:59:41PM -0800, Josh Berkus wrote:
> Hey, folks:
>
> I haven't configured a PostgreSQL server since version 11 (before that, I
> did quite a few).
>
> What's changed in terms of performance configuration since then? Have the
> fundamentals of
16 matches
Mail list logo
