Re: Performance killed with FDW when using CAST.

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: Jorge Torralba <jorge(dot)torralba(at)gmail(dot)com>, pgsql-admin(at)postgresql(dot)org
Subject: Re: Performance killed with FDW when using CAST.
Date: 2019-04-17 05:03:50
Message-ID: ea2a08fe7a53481ae973dadaf174dc2bf6e89a8e.camel@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-support pgsql-admin

Jorge Torralba wrote:
> We setup a FDW server for a large table that has an hstore data type as on eof the coums.
>
> When we run the query directly on the FDW server
>
> select * from recent_events where account_id = 1 AND (attributes -> 'account_incident_id')::integer = 2617116 limit 10;
>
> The response is 2ms . which is awesome.
>
> When we run it from the remote server where we have the server defined, the query never returns.
>
> Our server definition is as follows.
>
> (host 'fdwserver', dbname 'mydb', port '5432', fetch_size '1000', use_remote_estimate 'true', extensions 'hstore')

After debugging into this, it seems that the hstore operator -> cannot
be pushed down because of collation problems.

Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com

In response to

Responses

Browse pgadmin-support by date

  From Date Subject
Next Message Michel Feinstein 2019-04-17 06:19:56 pgAdmin Saved Password Security
Previous Message Jorge Torralba 2019-04-17 03:54:06 Re: Performance killed with FDW when using CAST.

Browse pgsql-admin by date

  From Date Subject
Next Message soumitra bhandary 2019-04-17 05:12:53 Fw: PostgreSQL 11.2 , missing X509_get_signature_nid symbol causes the standby to fail to start stream replication
Previous Message soumitra bhandary 2019-04-17 05:02:53 PostgreSQL 11.2 , missing X509_get_signature_nid symbol causes the standby to fail to start stream replication