Stefan Kaltenbrunner wrote: > >> Let's get a reasonable feature set implemented and then come back in 8.6 > >> to improve it. For example, there is no need for a special > >> 'replication' user (just use super-user), and monitoring should be > >> minimal until we have field experience of exactly what monitoring we > >> need. > >> > >> The final commit-fest is in 5 days --- this is not the time for design > >> discussion and feature additions. If we wait for SR to be feature > >> complete, with design discussions, etc, we will hopelessly delay 8.5 and > >> people will get frustrated. I am not saying we can't talk about design, > >> but none of this should be a requirement for 8.5. > > > > We can't add monitoring until we know what the performance > > characteristics are. Hmmm. And how will we know what the performance > > characteristics are, I wonder? > > well I would say we do exactly how we have done in the past with other > features - by debugging the stuff with low level tools until we fully > understand what it really is and then we can always add more > "accessible" stats.
Right, so what is the risk of shipping without any fancy monitoring? -- Bruce Momjian <br...@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + If your life is a hard drive, Christ can be your backup. + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
