Description: backend memory leak after massive 'CREATE/DROP USER'
wild guess says that its not really neccessarily a memory leak unless all the shared_buffers are getting consumed and its *still* growing...
CREATE USER adds a row to a system table, and DROP USER deletes that row, the table space will grow on disk until you do a VACUUM to release the free rows. Doing this without any VACUUM's will likely continue to allocate shared_buffers until they are used up (thats what they are for, after all).
have you run this process for hours and hours and many millions of users, such that the memory finally grows so big it crashes or errors out ?
---------------------------(end of broadcast)--------------------------- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
