On Sat, Sep 28, 2024, at 3:37 PM, Phil Stracchino wrote: > 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.
It is a very good database server. > Of course, the dead-simple way in *ANY* SQL engine is to just truncate > the table and then re-insert *one* correct row. Agreed. In this case, it's just one one row to be inserted, and it's simple. -- Dan Langille d...@langille.org _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
