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.
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
