On Mon, Jan 27, 2014 at 9:01 PM, Tom Lane <t...@sss.pgh.pa.us> wrote: > Amit Kapila <amit.kapil...@gmail.com> writes: >> On Fri, Jan 24, 2014 at 9:10 AM, Amit Kapila <amit.kapil...@gmail.com> wrote: > >> To proceed with the review of this patch, I need to know about >> whether appending version number or any other constant togli > >> Default Event Source name is acceptable or not, else for now >> we can remove this part of code from patch and handle non-default >> case where the change will be that pg_ctl will enquire non-default >> event_source value from server. > >> Could you please let me know your views about same? > > Unless I'm missing something, this entire thread is a tempest in a teapot, > because the default event_source value does not matter, because *by > default we don't log to eventlog*. The presumption is that if the user > turns on logging to eventlog, it's his responsibility to first make sure > that event_source is set to something appropriate. And who's to say that > plain "PostgreSQL" isn't what he wanted, anyway? Even if he's got > multiple servers on one machine, maybe directing all their logs to the > same place is okay by him.
I think it's matter of user preference, how exactly he wants the setup and as currently we don't have any strong reason to change default, so lets keep it intact. > Also, those who don't run multiple servers are probably not going to > thank us for moving their logs around unnecessarily. > > In short, I think we should just reject this idea as introducing more > problems than it solves, and not fully solving even the problem it > purports to solve. > > Possibly there's room for a documentation patch reminding users to > make sure that event_source is set appropriately before they turn > on eventlog. Okay, but in that case also right now pg_ctl doesn't know the value of event source, so I think thats a clear bug and we should go ahead and fix it. As you said, I think we can improve documentation in this regard so that user will be able to setup event log without any such problems. As part of this patch we can fix the issue (make pg_ctl aware for event source name) and improve documentation. With Regards, Amit Kapila. EnterpriseDB: http://www.enterprisedb.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
