From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Aidar Uldanov <aidar(at)donorbox(dot)org> |
Cc: | David Rowley <dgrowleyml(at)gmail(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #18690: A count function returns wrong value when using FDW |
Date: | 2024-11-06 15:29:31 |
Message-ID: | 3243407.1730906971@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Aidar Uldanov <aidar(at)donorbox(dot)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.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Aidar Uldanov | 2024-11-06 15:46:26 | Re: BUG #18690: A count function returns wrong value when using FDW |
Previous Message | Aidar Uldanov | 2024-11-06 15:10:57 | Re: BUG #18690: A count function returns wrong value when using FDW |