New answers tagged

1 vote

Postgresql: set default psql client encoding

I was facing the same error but changing from ANSI(X64) to Unicode(x64) in my ODBC conn fixed my issue.
user avatar
  • 11
3 votes

Valid characters for PostgreSQL session parameters

This is a breaking change introduced in PostgreSQL 14: Require custom server parameter names to use only characters that are valid in unquoted SQL identifiers (Tom Lane) https://www.postgresql.org/...
user avatar
0 votes

stored procedure runs fine in all sessions but one

I wish I had more rep so I could just leave a comment on Marcello's answer... But I would recommend against the global temp table as they're often a security risk since any session can access it's ...
user avatar
0 votes
Accepted

stored procedure runs fine in all sessions but one

I found a way out of this problem. I could not find out nor took the time to understand why exactly only one session was having this issue. This procedure of mine is packed with dynamic sql, and it ...
user avatar

Top 50 recent answers are included