Open meiyifei opened 5 years ago
It is, better to add a new GUC for max_result_bytes.
On Wed, Jul 3, 2019 at 4:35 PM meiyifei notifications@github.com wrote:
It depends on this value:max_result_bytes=14000000;
sprintf(url, "Driver={%s};url=http://%s:%s@ %s:%d/query?database=%s&max_result_bytes=14000000&buffer_size=3000000;",driver,user,pass,host,port,dbname);
We need to modify clickhouse-client.cpp and then recompile clickhouse_fdw.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/Percona-Lab/clickhousedb_fdw/issues/19?email_source=notifications&email_token=AA3NF4SE6LLU2JXPTZNZFWDP5RQEHA5CNFSM4H5DILKKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZDWYLA#issuecomment-507997228, or mute the thread https://github.com/notifications/unsubscribe-auth/AA3NF4STSITAM66DQSMHL3TP5RQEHANCNFSM4H5DILKA .
-- Ibrar Ahmed
I have started using the FDW and I am seeing unexpected results from queries which I suspect are due to the parameter max_result_bytes. Is this parameter set in clickhouse? Or is it a postgres parameter? Thanks!
It depends on this value:max_result_bytes=14000000;
sprintf(url, "Driver={%s};url=http://%s:%s@%s:%d/query?database=%s&max_result_bytes=14000000&buffer_size=3000000;",driver,user,pass,host,port,dbname);
We need to modify clickhouse-client.cpp and then recompile clickhouse_fdw.