> Hello, > Thanks a lot for your efforts. > Unfortunately, the patch did not solve the problem. > The query still issues the same "ERROR: invalid input syntax for integer: " > when > running at the replication pool, but being successful directly at one backend.
Ridiculous. The patch worked for me with the database and quey you gave. Can you show me pgpool log with log_per_node_statement enabled? Or try with 2.3-STABLE tree head (supposed to be released as 2.3.4 soon). If you have problem with grabbing CVS, I could personaly send you the tar ball (1.1MB). -- Tatsuo Ishii SRA OSS, Inc. Japan English: http://www.sraoss.co.jp/index_en.php Japanese: http://www.sraoss.co.jp > I made experiments rewriting the query connected at the pool: > expresso=# INSERT INTO > phpgw_cal(uid,title,owner,priority,is_public,category,last_update) > values('[email protected]','teste',1003,2,1,'','1282070139248'); > INSERT 17187 1 > expresso=# > > > expresso=# INSERT INTO > phpgw_cal(uid,title,owner,priority,is_public,category,last_update) > values('[email protected]','teste',1003,2,1,'', (date_part('epoch'::text, > ('now'::text)::timestamp(3) with time zone) * (1000)::double > precision)::bigint ); > INSERT 17188 1 > expresso=# > > > Is there a way to detect the column default type and rewrite the query for an > explicit type cast? > > Do you have more code suggestions? > Regards. > Andre Felipe > _______________________________________________ Pgpool-general mailing list [email protected] http://pgfoundry.org/mailman/listinfo/pgpool-general
