From: Thomas Kellerer <spam_eater@gmx.net>
To: pgsql-admin@postgresql.org
Subject: Re: Performance killed with FDW when using CAST.
Date: Wed, 17 Apr 2019 08:23:02 +0200
Message-ID: <q96go6$6fn4$1@blaine.gmane.org> (raw)
In-Reply-To: <ea2a08fe7a53481ae973dadaf174dc2bf6e89a8e.camel@cybertec.at>
References: <CACut7uSz_3JiJ4w80VrQYECtOAt1Ya5E=EdLBAJ2_DnYwqsjGA@mail.gmail.com>
<ea2a08fe7a53481ae973dadaf174dc2bf6e89a8e.camel@cybertec.at>
Laurenz Albe schrieb am 17.04.2019 um 07:03:
>> 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.
Do you happen to know if the JSONB operator -> (or ->>) can be pushed down?
Although I realize it would be a major change in the database design, maybe that would be a solution for Jorge.
Thomas
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: spam_eater@gmx.net
Subject: Re: Performance killed with FDW when using CAST.
In-Reply-To: <q96go6$6fn4$1@blaine.gmane.org>
* 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