incorrect bind variables substitution about pgreplay HOT 5 CLOSED

This is a shortcoming of pgreplay I hadn't been aware of.

Unfortunately there is nothing I can do about it.

In a query like this, the client would send data type information in the BIND message so that there is no ambiguity (otherwise you'd get just the same error).
But this information is not logged, and so pgreplay cannot replay it.

Unless you don't have a lot of these statements, it shouldn't be a big problem; all that happens is that you will have a slightly higher error count than in the original run.

I have added documentation about this to the README file.

from pgreplay.

Hi Luarenz,

I found a workaround for the issue.
Everything will work correctly if I replace in my example of the logged statement $1 + $2 with $1::nemeric + $2.

So, more general replacment is:

sed -i 's/($[0-9]+)( *[^,] *$)/\1::numeric\2/g' postgres_log_file.csv

Regards,
Yury

from pgreplay.

Hi Luarenz,

I found a workaround for the issue.
Everything will work correctly if I replace in my example of the logged statement $1 + $2 with $1::nemeric + $2.

So, more general replacment is:

sed -i 's/($[0-9]+)( *[^,] *$)/\1::numeric\2/g' postgres_log_file.csv

Regards,
Yury

from pgreplay.

Yes, certainly – if you write the query in a way that it does not require the data type information, it will replay without an error.

That sed command will certainly solve the problem if you have no other statements of the form $1 + $2 in your log. $1 could be a date value...

Do you want to keep this issue open for a certain reason?

from pgreplay.

Ah! You are right! I forgot about date type. But I'm sure I can write more complex handler of postgres log if needed.

Many thanks for answers. You may close the issue.

Regards,
Yury

from pgreplay.