BUG #16148: Query on Large table hangs in ETL flows and gives out of memory when run in pgAdmin4

From: PG Bug reporting form <noreply(at)postgresql(dot)org>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: scottvolkers(at)gmail(dot)com
Subject: BUG #16148: Query on Large table hangs in ETL flows and gives out of memory when run in pgAdmin4
Date: 2019-12-04 14:19:56
Message-ID: 16148-ed1cc02fdf2200ec@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 16148
Logged by: Scott Volkers
Email address: scottvolkers(at)gmail(dot)com
PostgreSQL version: 9.5.15
Operating system: PostgreSQL 9.5.15 on x86_64-pc-linux-gnu, compiled
Description:

We have a large table and the error occurs with this where clause:
FROM "elliedb"."documentlog" WHERE dcmodifiedutc>(extract(epoch from
TIMESTAMP '2019-11-15 11:30:51')*1000)

When we reduce the scope to current time - 4 hours the query works within 44
seconds.
where dcmodifiedutc > '1575282651000'

Is this expected? Is this a version issue being only 9.5? It seems the
timestamp conversion would be done once and applied to the filter, but it
seems to ballooning the query result being aggregated for the where
clause?
Thank you.

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2019-12-04 15:48:58 Re: pg_dump losing index column collations for unique and primary keys
Previous Message Tom Lane 2019-12-04 14:03:26 Re: BUG #16147: postgresql 12.1 (from homebrew) - pg_restore -h localhost --jobs=2 crashes