Re: set autovacuum=off
От | Filippos Kalamidas |
---|---|
Тема | Re: set autovacuum=off |
Дата | |
Msg-id | CANUP4k13Lqc5HfsEMGaZKsycNxwJ4A5YW4OBC2tLycjY=DwXGQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: set autovacuum=off (Alessandro Gagliardi <alessandro@path.com>) |
Ответы |
Re: set autovacuum=off
|
Список | pgsql-performance |
yup there is. the parameter checkpoint_segments does not require a restart of the server, just a reload :)
On Fri, Feb 24, 2012 at 12:54 AM, Alessandro Gagliardi <alessandro@path.com> wrote:
On Thu, Feb 23, 2012 at 1:11 PM, Peter van Hardenberg <pvh@heroku.com> wrote:My hunch is still that your issue is lock contention.How would I check that? I tried looking at pg_locks but I don't know what to look for.We have many customers who do much more than this throughput, thoughI'm not sure what level of resourcing you're current at. You might
consider experimenting with a larger system if you're having
performance problems.Heh. I thought you might say that. :) It's definitely worth considering, but as youmight expect, I want to exhaust other options first. For customers who do much more (or even comparable) throughput, can you tell me how big of a system they require?
Also, as per Andy's suggestion, I'd like to try doubling checkpoint_segments. However, it appears that that is one of those variables that I cannot change from pgAdmin. I don't suppose there's any way to change this without rebooting the database?
В списке pgsql-performance по дате отправления: