On Tuesday, August 31, 2021, Ninad Shah <
nshah.postgres@gmail.com> wrote:
Hi Karsten,
I apologize for the delayed response.
There is no script-related transfer happening here. It creates an issue while using "bash@" inside a column.
That wasn’t what was meant. Ignore the “why” for the moment, the theory is something in the network or OS sees that string of data and fires off a rule that causes the data to be filtered. Period. The comment about “bash script” was just saying that whatever the “something” is might be guessing that the text sequence “bash@“ has something to do with bash scripts. It was just a hint. But regardless of why the false positive exists the theory is that there is one happening in the environment externally to any PostgreSQL related software.
David J.
