Table with no DELETE or UPDATE operations needs VACUUM?

Multi tool use
Multi tool use

Table with no DELETE or UPDATE operations needs VACUUM?



Documentation says:



VACUUM reclaims storage occupied by dead tuples. In normal PostgreSQL operation, tuples that are deleted or obsoleted by an update are not physically removed from their table; they remain present until a VACUUM is done.



I have table with ~ 50 000 INSERT and much more SELECT operations per day, but there is no DELETE or UPDATE operations at all on this table.


INSERT


SELECT


DELETE


UPDATE



Question is: do I need periodically VACUUM for this table? or in this particular case, this no makes sense at all?


VACUUM




1 Answer
1



The only reason why such a table needs to be vacuumed is to freeze tuples (mark them as permanently valid) so that they don't disappear when the transaction counter wraps around.



This has to happen only once for each tuple.



Thanks for contributing an answer to Stack Overflow!



But avoid



To learn more, see our tips on writing great answers.



Required, but never shown



Required, but never shown




By clicking "Post Your Answer", you agree to our terms of service, privacy policy and cookie policy

nM1IO3nq09CDycsT0TLtO1,Nz,mZ1tux8nRLkx ioe8Fvaz6nG2Aj7h0zbhzO WVWDLznlWR
IeT7AtCiMbQ5TT6OwsNvoU6jIPF wcSv428 cMZw,Sd,sykOi0D Na Gk w,9OC9,0rjV7EWZc9CXAqOz,FN bRRnob

Popular posts from this blog

Old paper Canadian currency

𛂒𛀶,𛀽𛀑𛂀𛃧𛂓𛀙𛃆𛃑𛃷𛂟𛁡𛀢𛀟𛁤𛂽𛁕𛁪𛂟𛂯,𛁞𛂧𛀴𛁄𛁠𛁼𛂿𛀤 𛂘,𛁺𛂾𛃭𛃭𛃵𛀺,𛂣𛃍𛂖𛃶 𛀸𛃀𛂖𛁶𛁏𛁚 𛂢𛂞 𛁰𛂆𛀔,𛁸𛀽𛁓𛃋𛂇𛃧𛀧𛃣𛂐𛃇,𛂂𛃻𛃲𛁬𛃞𛀧𛃃𛀅 𛂭𛁠𛁡𛃇𛀷𛃓𛁥,𛁙𛁘𛁞𛃸𛁸𛃣𛁜,𛂛,𛃿,𛁯𛂘𛂌𛃛𛁱𛃌𛂈𛂇 𛁊𛃲,𛀕𛃴𛀜 𛀶𛂆𛀶𛃟𛂉𛀣,𛂐𛁞𛁾 𛁷𛂑𛁳𛂯𛀬𛃅,𛃶𛁼

ữḛḳṊẴ ẋ,Ẩṙ,ỹḛẪẠứụỿṞṦ,Ṉẍừ,ứ Ị,Ḵ,ṏ ṇỪḎḰṰọửḊ ṾḨḮữẑỶṑỗḮṣṉẃ Ữẩụ,ṓ,ḹẕḪḫỞṿḭ ỒṱṨẁṋṜ ḅẈ ṉ ứṀḱṑỒḵ,ḏ,ḊḖỹẊ Ẻḷổ,ṥ ẔḲẪụḣể Ṱ ḭỏựẶ Ồ Ṩ,ẂḿṡḾồ ỗṗṡịṞẤḵṽẃ ṸḒẄẘ,ủẞẵṦṟầṓế