SQL converter
Rewrite quoting, escaping, row limits and function names between 16 dialects, with a list of what it refused to guess at.
Google BigQuery query
PostgreSQL query
What it changed
current timestampCURRENT_TIMESTAMP1 place
What you still need to do
1 thing this tool will not guess at
Array subscript
Google BigQuery counts array positions from 0, PostgreSQL from 1: the same arr[1] is the first element in one and the second in the other, with no error. Adjust every index by one.
Anything left in this list was recognised and left as it was on purpose. A function renamed to one that takes its arguments in a different order produces SQL that runs and returns the wrong rows, which is worse than SQL that fails.
Converting Google BigQuery to PostgreSQL: Key Syntax Differences
Translating SQL queries between Google BigQuery and PostgreSQL involves subtle dialect differences that standard text find-and-replace often misses. Everything below is processed entirely in your browser using SQLParity.
Identifier Quoting
Google BigQuery: `name`
PostgreSQL: "name"
String Literal Escaping
Google BigQuery: Quotes are escaped with backslash (\'), backslash is an escape character.
PostgreSQL: Quotes are doubled (''), backslash is literal.
Null-Safe Equality
PostgreSQL: colA IS DISTINCT FROM colB
Why In-Browser SQL Conversion Matters
Database migrations frequently involve proprietary business logic, sensitive table schemas, and production column names. When converting SQL between Google BigQuery and PostgreSQL, SQLParity executes all parsing, tokenization, and code rewriting locally in your browser. Zero queries or schemas are transmitted to remote servers.