I can confirm that was the issue, after removing the expression and using
only what was indexed it definitely fixed the query plan. I appreciate all
the help you've given me, I didn't really think to look there but it makes
a ton of sense that a filter on the database would only work well if it's
i
On Sat, 6 Jun 2020 at 14:49, Cedric Leong wrote:
> It's less of a complaint rather than just a warning not to do what I did.
My point was really that nobody really knew what you did or what you
did it on. So it didn't seem like a worthwhile warning as it
completely lacked detail.
> These tests a
It's less of a complaint rather than just a warning not to do what I did.
Version:
PostgreSQL 11.6 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 4.9.3, 64-bit
The actual command list would probably be impractical to put in here just
because the majority of it would just be creating a large amount
On Sat, 6 Jun 2020 at 14:12, Cedric Leong wrote:
> Somewhat unrelated but note to anyone who wants to swap out partition keys.
> Don't create a clone of the table with the new partition key and insert data.
> It messes up the query planner massively and makes everything much slower.
That compla
Somewhat unrelated but note to anyone who wants to swap out partition keys.
Don't create a clone of the table with the new partition key and insert
data. It messes up the query planner massively and makes everything much
slower.
On Mon, May 25, 2020 at 12:48 AM Tom Lane wrote:
> Cedric Leong wr
> "Bulk loads ...",
As I see - There is an interesting bulkload benchmark:
"How Bulkload performance is affected by table partitioning in PostgreSQL"
by Beena Emerson (Enterprisedb, December 4, 2019 )
*SUMMARY: This article covers how benchmark tests can be used to
demonstrate the effect of
pá 5. 6. 2020 v 12:07 odesílatel Krzysztof Olszewski
napsal:
> I have problem with one of my Postgres production server. Server works
> fine almost always, but sometimes without any increase of transactions or
> statements amount, machine gets stuck. Cores goes up to 100%, load up to
> 160%. When
De: "Krzysztof Olszewski"
Para: pgsql-performance@lists.postgresql.org
Enviadas: Sexta-feira, 5 de junho de 2020 7:07:02
Assunto: Postgresql server gets stuck at low load
BQ_BEGIN
I have problem with one of my Postgres production server. Server works fine
almost always, but sometime
I have problem with one of my Postgres production server. Server works fine
almost always, but sometimes without any increase of transactions or
statements amount, machine gets stuck. Cores goes up to 100%, load up to
160%. When it happens then there are problems with connect to database and
even i
