Convert pgAdmin backup to SQLite3

Working from a pgAdmin backup

pgAdmin's Backup dialog is a front end to pg_dump, so what you end up with depends on which format you picked in it - and the default is not plain SQL, which surprises people expecting a file they can read.

• →In pgAdmin's server and container modes the backup is written on the machine running pgAdmin rather than on yours, under that installation's storage directory for your login. Fetch it with pgAdmin's own file manager before you can upload it anywhere.
• →If the dialog refused to produce a file at all and complained that a utility was not found, that is its Binary Path preference pointing at no pg_dump. It is a pgAdmin setting, not a problem with your database.
• →The dialog's "Do not save Owner" and "Do not save Privileges" toggles make no difference to the result: those statements are stripped when the archive is unpacked, whichever way you set them.

The .sqlite3 name and what carries over

The 3 in sqlite3 is the file format version and the name of the command-line tool, not a property of your conversion. One database file arrives, and the two things worth knowing about it are what it is called and what it leaves behind.

• →The file inside the zip is always database.sqlite, whichever spelling brought you to this page. Rename it to database.sqlite3, or to whatever a framework expects, once you have it - the header is what identifies it, never the extension.
• →An auto-increment column arrives holding all of its values and nothing that assigns new ones. No AUTOINCREMENT keyword is written, and the column is declared BIGINT rather than exactly INTEGER, so it is not an alias for the rowid either: rows you insert later have to supply their own key.
• →Only the rows are transactional. The very first CREATE TABLE runs in autocommit, and everything after it - that table's rows, and every later table - sits in one transaction that commits after the last row. A conversion that fails partway therefore leaves a file holding an empty shell of the first table and nothing else. You never receive that file: the zip is only assembled once the writer has returned.

Reading pgAdmin backup

• →Reads pg_dump custom-format archives (.backup, .dump) — pgAdmin's default backup option — as well as plain SQL dumps.
• →Data written as COPY blocks is read, not just INSERT statements. COPY is pg_dump's default, so a reader that only understands INSERT returns your tables with none of their rows.
• →Primary keys declared by a later ALTER TABLE, which is how pg_dump writes them, are preserved.

Writing SQLite3

• →Columns get real declared types rather than everything being TEXT.
• →Primary keys and NOT NULL constraints are preserved.
• →A money column is declared NUMERIC(10,2), but that declaration does not stop SQLite’s own numeric affinity from converting the inserted value into a float once it lands, so 19.99 can come back with a rounding tail. Pick the DuckDB target instead when the exact decimal has to survive.

Convert pgAdmin backup to something else

• MySQL
• PostgreSQL
• Oracle
• SQL Server
• DuckDB
• CSV
• Excel

Convert something else to SQLite3

• CSV
• Excel
• SQL dump
• DBF
• JSON
• XML
• Parquet
• DuckDB
• MS Access