You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I restore a dump to my local database, all sequences for all tables are set to start value of 1.
I restored a Greenmask dump into a file (using pg_restore --file=1738263512345.sql greenmask_local_storage/1738263512345) and then grep that file (cat 1738263512345.sql | grep -i 'pg_catalog\.setval'). I noticed that all the SELECT pg_catalog.setval('"public"."my_table_id_seq"', 1234567, true) statements don't have semicolons at the end. All other statements in that file do have a semicolon at the end.
I also did a manual dump in a directory format leaving other settings to default and then repeated the above steps. The pg_catalog.setval statements in that file have a semicolon at the end.
The text was updated successfully, but these errors were encountered:
Hey,
Thank you for your work on this tool!
When I restore a dump to my local database, all sequences for all tables are set to start value of 1.
I restored a Greenmask dump into a file (using
pg_restore --file=1738263512345.sql greenmask_local_storage/1738263512345
) and then grep that file (cat 1738263512345.sql | grep -i 'pg_catalog\.setval'
). I noticed that all theSELECT pg_catalog.setval('"public"."my_table_id_seq"', 1234567, true)
statements don't have semicolons at the end. All other statements in that file do have a semicolon at the end.I also did a manual dump in a directory format leaving other settings to default and then repeated the above steps. The
pg_catalog.setval
statements in that file have a semicolon at the end.The text was updated successfully, but these errors were encountered: