Re: Performance killed with FDW when using CAST.

From: Thomas Kellerer <spam_eater(at)gmx(dot)net>
To: pgsql-admin(at)postgresql(dot)org
Subject: Re: Performance killed with FDW when using CAST.
Date: 2019-04-17 06:23:02
Message-ID: q96go6$6fn4$1@blaine.gmane.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-support pgsql-admin

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

In response to

Responses

Browse pgadmin-support by date

  From Date Subject
Next Message Dave Page 2019-04-17 08:05:43 Re: pgAdmin Saved Password Security
Previous Message Michel Feinstein 2019-04-17 06:19:56 pgAdmin Saved Password Security

Browse pgsql-admin by date

  From Date Subject
Next Message Devrim Gündüz 2019-04-17 07:55:12 Re: Fw: PostgreSQL 11.2 , missing X509_get_signature_nid symbol causes the standby to fail to start stream replication
Previous Message Michel Feinstein 2019-04-17 06:17:19 Re: pgAdmin Saved Password Security