Re: Performance killed with FDW when using CAST. - Mailing list pgsql-admin

From Laurenz Albe
Subject Re: Performance killed with FDW when using CAST.
Date
Msg-id ea2a08fe7a53481ae973dadaf174dc2bf6e89a8e.camel@cybertec.at
Whole thread Raw
In response to Performance killed with FDW when using CAST.  (Jorge Torralba <jorge.torralba@gmail.com>)
Responses Re: Performance killed with FDW when using CAST.  (Thomas Kellerer <spam_eater@gmx.net>)
List 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




pgsql-admin by date:

Previous
From: soumitra bhandary
Date:
Subject: PostgreSQL 11.2 , missing X509_get_signature_nid symbol causes thestandby to fail to start stream replication
Next
From: pavan95
Date:
Subject: Re: Too many serialization errors in production