To avoid a dump/restore, use this: psql -o /dev/null -c "select * from table for update" database
Using the last releases of the major versions solve the bug for me. Best regards Em qua, 13 de mar de 2019 às 09:29, Mariel Cherkassky < mariel.cherkas...@gmail.com> escreveu: > Hey, > The logs are full of info that I cant share. However, it full of the next > messages : > ERROR: found xmin 16804535 from before relfrozenxid 90126924 > CONTEXT: automatic vacuum of table db1.public.table_1" > ... > > What I'm trying to understand here is if the bug was fixed or not. In the > first time it appeared the dump and the restore solved the issue. However, > is happened the second time on a different table. So basically I'm trying > to understand how to solve it permanently. > > the dump command ; pg_dump -d db -U username -t table_name -f table.sql > I dropped the old table and restored it : > drop table table_name; > psql -d db -U username -f table.sql > > בתאריך יום ד׳, 13 במרץ 2019 ב-14:24 מאת Adrien NAYRAT < > adrien.nay...@anayrat.info>: > >> On 3/12/19 8:58 AM, Mariel Cherkassky wrote: >> > Apparently the issue appeared again in the same database but on >> > different table . In the last time dumping and restoring the table >> > helped. However, I dont understand why another table hit the bug if it >> > was fixed in 9.6.9 while my db version is 9.6.10. >> >> Hello, >> >> Could you provide more details (logs...) and remind how you perform >> database dump/restore? >> >> This will help community to help you ;) >> >> Regards, >> >
