Joao Afonso <joaoaafonso@xxxxxxxxx> writes: > So (finally), my question is why does this happen? Using instead on > the users_util insert rule shouldn't discard the original query and > rewrite it according to the specified on the rule?? Is this a problem > of dblink? I hadn't noticed the dblink_current_query() function before, but now that I see it, I consider it a pretty bad idea. It certainly will not help you the way you are hoping, because what it returns is the text of the interactive command the backend is currently working on --- which could be indefinitely far removed from the operation your rule is firing for. regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to majordomo@xxxxxxxxxxxxxx so that your message can get through to the mailing list cleanly