Re: Increasing WAL usage followed by sudden drop
От | delongboy |
---|---|
Тема | Re: Increasing WAL usage followed by sudden drop |
Дата | |
Msg-id | 1345226019192-5720250.post@n5.nabble.com обсуждение исходный текст |
Ответ на | Re: Increasing WAL usage followed by sudden drop (Joshua Berkus <josh@agliodbs.com>) |
Ответы |
Re: Increasing WAL usage followed by sudden drop
|
Список | pgsql-performance |
Josh Berkus wrote > >> We are not doing anything to postgres that would cause the rise and >> drop. >> Data base activity is pretty consistent. nor are we doing any kind >> of >> purge. This week the drop occurred after 6 days. We are thinking it >> must >> be some kind of internal postgres activity but we can't track it >> down. > > Well, we certainly can't figure it out on this list by blind guessing ... > Have to agree with you there. Unfortunately this is where we've ended up. What can we look at and/or show that would help us to narrow it down? Is there anyway we can look into the wal file and see exactly what is being sent? I think this might actually give us the most insight. -- View this message in context: http://postgresql.1045698.n5.nabble.com/Increasing-WAL-usage-followed-by-sudden-drop-tp5719567p5720250.html Sent from the PostgreSQL - performance mailing list archive at Nabble.com.
В списке pgsql-performance по дате отправления: