Re: Performance killed with FDW when using CAST.
| От | Laurenz Albe |
|---|---|
| Тема | Re: Performance killed with FDW when using CAST. |
| Дата | |
| Msg-id | ea2a08fe7a53481ae973dadaf174dc2bf6e89a8e.camel@cybertec.at обсуждение исходный текст |
| Ответ на | Performance killed with FDW when using CAST. (Jorge Torralba <jorge.torralba@gmail.com>) |
| Ответы |
Re: Performance killed with FDW when using CAST.
|
| Список | 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 по дате отправления: