See psycopg Identifier for binding table names

https://www.psycopg.org/psycopg3/docs/api/sql.html#psycopg.s...

Since at least two people noticed, I would just say that the insert-select-insert approach was added later, after I took some inspiration from Django's implementation of get_or_create.

If you store large jsonb values in the database, storing them out of line may be a good thing - for example, you can query metadata much faster.

Also, worth mentioning that jsonb is only benefitial when you plan on indexing/manipulating the data in the database. Otherwise, using json type may be a better choice (smaller size, stored as text, parsed on demand)

I used excalidraw.com

You can utilize transactional DDL for that

https://hakibenita.com/sql-tricks-application-dba#make-index...

I'm always looking for new copy tricks. Is "copy" a temporary table? Or a variable...?

Temporary table. Although looking at the docs it seems CREATE TABLE AS is the recommended syntax. https://www.postgresql.org/docs/13/sql-createtableas.html

    CREATE TEMP TABLE "copy" AS
    SELECT * FROM foobar;

See relevant section in the article:

https://hakibenita.com/python-mypy-exhaustive-checking#the-f...

Starting at PostgreSQL 12 you don't even have to feel bad about all of those CTE's.

See this

https://hakibenita.com/fast-load-data-python-postgresql