On 9/28/24 15:15, Dan Langille wrote:
I found a solution after some searching: use ctid
From
https://www.postgresql.org/docs/current/ddl-system-columns.html#DDL-SYSTEM-COLUMNS-CTID
"The physical location of the row version within its table. Note that although the
ctid can be used to locate the row version very quickly, a row's ctid will change if it
is updated or moved by VACUUM FULL. Therefore ctid is useless as a long-term row
identifier. A primary key should be used to identify logical rows."
Ah, I have very little experience with postgresql and have tried to keep
it that way.
Of course, the dead-simple way in *ANY* SQL engine is to just truncate
the table and then re-insert *one* correct row.
--
Phil Stracchino
Fenian House Publishing
ph...@caerllewys.net
p...@co.ordinate.org
Landline: +1.603.293.8485
Mobile: +1.603.998.6958
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
