You are right but the correct query is the one in the attached file. What
we want to do here is to force psql to send the "wrong data types" to
postgres and, as a result of this, get a bad plan.
Cheers,
Jose Osinde
On Thu, Aug 25, 2022 at 3:48 PM Ranier Vilela wrote:
> Em qui., 25 de ago. de 20
Em qui., 25 de ago. de 2022 às 10:43, Jose Osinde
escreveu:
>
> Dear Depesz, Laurenz,
>
> Thanks very much for the fast responses. They are actually correct and
> saved me a lot of time. I couldn't test the cast from the Java test but
> this is something I can deal with later on (most probably up
Dear Depesz, Laurenz,
Thanks very much for the fast responses. They are actually correct and
saved me a lot of time. I couldn't test the cast from the Java test but
this is something I can deal with later on (most probably updating the
column types to text in the database side instead). But what I
On Thu, 2022-08-25 at 11:10 +0200, hubert depesz lubaczewski wrote:
> Hi,
>
> On Thu, Aug 25, 2022 at 10:49:51AM +0200, Jose Osinde wrote:
> > select logical_identifier, version_id, lastproduct
> > from test_product_ui_partition.product_ui pui
> > where pui.mission_id='urn:esa:psa:context:i
Hi,
On Thu, Aug 25, 2022 at 10:49:51AM +0200, Jose Osinde wrote:
> select logical_identifier, version_id, lastproduct
>from test_product_ui_partition.product_ui pui
> where pui.mission_id='urn:esa:psa:context:investigation:mission.em16'
> and
> pui.logical_identifier='urn:esa:psa:em
Dear all,
After detecting some performance issues accessing a partitioned table in a
postgres database we created a simple Java test to analyse the possible
causes of this problem. The test is very simple. It just creates a database
connection and executes a query on a partitioned table including
