sandord / respawn.postgres Goto Github PK

• Figure out what versions of Postgres the queries are compatible with.
• Attempt to improve compatibility. The database structure hash query may be sensitive to Postgres updates, either breaking or missing new parts. Perhaps we can iterate the columns that are currently selected statically.
• Update docs accordingly
• Provide a mechanism that can select compatible queries for certain Postgres version ranges.

Database entity names are currently validated (to mitigate SQL injection vulnerabilities), allowing alpha numeric characters and '_' and '-' only. It's likely that this is too stringent and sooner or later someone will hit this wall.

Proposed solution: allow all characters except for those that pose an SQL injection risk.

Respawn: 3.20
Npgsql: 4.0.5

I tried to use PostgresCheckpoint and got this error

Npgsql.PostgresException : 42703: column p.consrc does not exist Data: Severity: ERROR InvariantSeverity: ERROR SqlState: 42703 MessageText: column p.consrc does not exist Hint: Perhaps you meant to reference the column "p.conkey" or the column "p.conbin". Position: 3309 File: parse_relation.c Line: 3523 Routine: errorMissingColumn

After googling I've found out the problem is PG12 removed the pg_constraint.consrc, this is tracked by PG12 removed the pg_constraint.consrc.
Possible solution: downgrading to PG11 should work until a fix is released.

Well... What if I want to stay in PG12?