oh sorry, I might forget to update int to bigint there. Actually both should be bigint. First I tried with int type and it works well and after changing to bigint I got the wrong count value.
Aidar Uldanov <aidar@donorbox.org> writes: > David, after some troubleshooting I found out that the issue with FWD and > bigint values, so when column type int then it works well but after > changing to a bigint type a count() function returns the wrong value.
> create table transactions( > id serial primary key, > amount int, > org_id int, > recurring_payment_id int REFERENCES recurring_payments(id) > ); > ... > CREATE FOREIGN TABLE transactions_f ( > id serial, > amount bigint, > org_id int, > recurring_payment_id int > ) > SERVER foreign_server > OPTIONS (schema_name 'public', table_name 'transactions');
While it's sort of interesting that that misbehaves, I do not believe that postgres_fdw promises to work correctly with foreign-table definitions that don't match the remote table's actual column datatypes.
