Back up your PG database (just in case), then run thisL SELECT setval('the_primary_key_sequence', (SELECT MAX(the_primary_key) FROM the_table)+1) If the first value is higher than the second value, your sequence is out of sync. Second, supply a list of comma-separated values in a parentheses (value1, value2. SELECT nextval('the_primary_key_sequence') VALUES appearing within INSERT is a special case (because the desired column types are known from the INSERT 's target table, and need not be inferred by scanning the VALUES list), so it can handle larger lists than are practical in other contexts. In this syntax: First, specify the name of the table ( tablename) that you want to insert data after the INSERT INTO keywords and a list of comma-separated columns ( colum1, column2. If you use the query clause to insert rows from a query, you of. At any rate, to see if your values are out of sync, run these two commands: SELECT MAX(the_primary_key) FROM the_table Use of the RETURNING clause requires SELECT privilege on all columns mentioned in RETURNING. Call it a "bug by design", but it seems that you have to manually reset the a primary key index after restoring from a dump file. That likely means that the primary key sequence in the table you're working with has somehow become out of sync, likely because of a mass import process (or something along those lines). One can insert one or more rows specified by value expressions, or zero or more rows resulting from a query. One can insert one or more rows specified by value expressions, or zero or more rows resulting from a query. If you get this message when trying to insert data into a PostgreSQL database:ĮRROR: duplicate key violates unique constraint Description INSERT inserts new rows into a table.
POSTGRESQL INSERT INTO SELECT AND VALUES HOW TO
How to fix PostgreSQL error "duplicate key violates unique constraint" This post helped me solve my problem, not sure what went wrong:
0 kommentar(er)
