Re: [EXT EMAIL] Re: First Time Starting Up PostgreSQL and Having Problems
От | Tom Lane |
---|---|
Тема | Re: [EXT EMAIL] Re: First Time Starting Up PostgreSQL and Having Problems |
Дата | |
Msg-id | 8328.1561042535@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | RE: [EXT EMAIL] Re: First Time Starting Up PostgreSQL and HavingProblems (Brent Bates <BBates@langleyfcu.org>) |
Ответы |
Re: [EXT EMAIL] Re: First Time Starting Up PostgreSQL and HavingProblems
RE: [EXT EMAIL] Re: First Time Starting Up PostgreSQL and HavingProblems |
Список | pgsql-general |
Brent Bates <BBates@langleyfcu.org> writes: > I found the problem. I cleared everything out and started from scratch, then slowly added my changes back to theconfiguration files. The problem was in the postgresql.conf. At the bottom of the file I had uncommented all the ‘include’lines, so they looked like this: > include_dir = '' # include files ending in '.conf' from > # a directory, e.g., 'conf.d' > include_if_exists = '' # include file only if it exists > include = '' # include file > The first one is what caused all the headaches. I recommented out these lines and everything works now. Thanks for allthe quick suggestions. Ah-hah! I wonder if we should disallow empty values for these GUCs? And/or put in some kind of test for recursive opening of the same config file? I don't think it'd occurred to anyone that it's this easy to get the code to try to do that. regards, tom lane
В списке pgsql-general по дате отправления: