Hello, I'm simulating the upgrade to 6.0.8 with postgresql. During the DB-update-to-6 script I see : - Error: The following sequences with possible wrong names have been found. Please rename them manually. pop3_account_id_seq standard_response_id_seq standard_response_attachment_id_seq system_user_id_seq ticket_link_ticket_id_master_seq ticket_link_ticket_id_slave_seq How I have to rename to? is it documented in some way this? - the process remain stuck on: Requirement check for: Create entries in new article table ... I see that the script it's waiting a running a query: SELECT COUNT(article_flag.article_id) FROM article_flag WHERE (article_flag.article_id NOT IN (SELECT article.id FROM article)) OR (article_flag.article_id IN (SELECT article.id FROM article WHERE article.ticket_id NOT IN (SELECT ticket.id FROM ticket))) the query it's running since over two hour... I digged...this is the planner of the query: QUERY PLAN ------------------------------------------------------------------------------------------------- Aggregate (cost=18890210286.49..18890210286.49 rows=1 width=8) -> Seq Scan on article_flag (cost=9800.98..18890209735.48 rows=220403 width=8) Filter: ((NOT (SubPlan 1)) OR (SubPlan 3)) SubPlan 1 -> Materialize (cost=0.00..63789.83 rows=545989 width=8) -> Seq Scan on article (cost=0.00..58926.89 rows=545989 width=8) SubPlan 3 -> Materialize (cost=9800.98..72524.81 rows=272994 width=8) -> Seq Scan on article article_1 (cost=9800.98..70092.84 rows=272994 width=8) Filter: (NOT (hashed SubPlan 2)) SubPlan 2 -> Seq Scan on ticket (cost=0.00..9183.58 rows=246958 width=8) (12 rows) my article table it's 646MB and contain 500k records. It's not so huge but this query seems not optimised in order to work fast on this scenario. What do you suggest to speedup the process? Thanks Matteo