From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Jorge Torralba <jorge.torralba@gmail.com>
To: pgsql-admin@postgresql.org
Subject: Re: Performance killed with FDW when using CAST.
Date: Wed, 17 Apr 2019 07:03:50 +0200
Message-ID: <ea2a08fe7a53481ae973dadaf174dc2bf6e89a8e.camel@cybertec.at> (raw)
In-Reply-To: <CACut7uSz_3JiJ4w80VrQYECtOAt1Ya5E=EdLBAJ2_DnYwqsjGA@mail.gmail.com>
References: <CACut7uSz_3JiJ4w80VrQYECtOAt1Ya5E=EdLBAJ2_DnYwqsjGA@mail.gmail.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: laurenz.albe@cybertec.at, jorge.torralba@gmail.com
Subject: Re: Performance killed with FDW when using CAST.
In-Reply-To: <ea2a08fe7a53481ae973dadaf174dc2bf6e89a8e.camel@cybertec.at>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox