Re: Missing messages
Tom Ekberg <[email protected]>
| Newsgroups | gmane.comp.bug-tracking.roundup.user |
|---|---|
| Message-ID | <CO3PR08MB7957E4C1DEF5F86C1C11CDE9CA149@CO3PR08MB7957.namprd08.prod.outlook.com> |
Investigating this further, I ran this query
uw_chemistry=# SELECT * FROM msg__journal WHERE params LIKE '%476%';
nodeid | date | tag | action | params
--------+-------------------------+-----+--------+------------------------------
1514 | 2017-12-07 16:10:20.203 | 33 | link | ('issue', '476', 'messages')
1514 | 2017-12-12 22:55:13.576 | 33 | unlink | ('issue', '476', 'messages')
1515 | 2017-12-12 22:56:15.213 | 33 | link | ('issue', '476', 'messages')
It looks like user 33 unlinked message 1514. It looks like all this did was to remove it from the issue_messages table. Should roundup have 'retired' message 1514 too?
Tom Ekberg
Senior Computer Specialist
Department of Laboratory Medicine and Pathology
4th Floor, Pat Steel Building, currently WFH
Home: (253) 561-2509
Email: [email protected]<mailto:[email protected]>
From: Tom Ekberg <[email protected]<mailto:[email protected]>>
Sent: Thursday, December 1, 2022 1:15 PM
To: Roundup Users ([email protected]<mailto:[email protected]>) <[email protected]<mailto:[email protected]>>
Subject: [Roundup-users] Missing messages
I'm migrating our tracker to a new Ubuntu host and to Postgresql 15. I was poking around on the new uw_chemistry tracker and noticed an issue that showed 1 message, but there were 2 in the history. Neither one was retired. The problem was that there was only one message in the issue_messages mapping table for that issue. I looked at the production tracker and that issue had the same problem. I ended up doing an INSERT to have both messages show up. Now that issue shows the right messages for production and dev. I noticed 2 other issues, there are problem more, in the uw_chemistry tracker that have this same problem.
We have gone through at least 3 database transfers, moving to new OSs and new versions of Postgresql. I think the first one used roundup-admin to transfer the data. The last 2 have used a combination of DB dumps+rsync to transfer the data. The run time for roundup-admin export/import is hours for some of our larger trackers so we don't use that anymore.
I plan on writing some python+sql to see how many problem issues there are.
Has anyone had trouble with Postgresql deleting entries from a tracker mapping table?
Tom Ekberg
Senior Computer Specialist
Department of Laboratory Medicine and Pathology
4th Floor, Pat Steel Building, currently WFH
Home: (253) 561-2509
Email: [email protected]<mailto:[email protected]>
_______________________________________________
Roundup-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/roundup-users