Re: [bug fix] pg_ctl always uses the same event source
От | Tom Lane |
---|---|
Тема | Re: [bug fix] pg_ctl always uses the same event source |
Дата | |
Msg-id | 10978.1390512335@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: [bug fix] pg_ctl always uses the same event source (Peter Eisentraut <peter_e@gmx.net>) |
Ответы |
Re: [bug fix] pg_ctl always uses the same event source
Re: [bug fix] pg_ctl always uses the same event source |
Список | pgsql-hackers |
Peter Eisentraut <peter_e@gmx.net> writes: > On 1/23/14, 4:08 PM, Robert Haas wrote: >> Why wouldn't that be necessary with your approach, too? I mean, if >> there's a GUC that controls the event source name, then it can be >> changed between restarts, regardless of what you call it. > I don't know if it's practical, but the logical conclusion here would be > to use an identifier that you cannot change, such as the system identifier. That particular ID would be a horrid choice, because we don't try very hard to ensure it's unique. In particular, a standby server on the same machine as the master (not an uncommon case, at least for testing purposes) would be a guaranteed fail with that approach. I'm still not clear on why we can't just use the port number. regards, tom lane
В списке pgsql-hackers по дате отправления: