Re: pg_upgrade documentation improvement patch
| От | Tom Lane |
|---|---|
| Тема | Re: pg_upgrade documentation improvement patch |
| Дата | |
| Msg-id | 20453.1460555409@sss.pgh.pa.us обсуждение |
| Ответ на | Re: pg_upgrade documentation improvement patch (Peter Eisentraut <peter_e@gmx.net>) |
| Ответы |
Re: pg_upgrade documentation improvement patch
Re: pg_upgrade documentation improvement patch |
| Список | pgsql-hackers |
Peter Eisentraut <peter_e@gmx.net> writes:
> Interesting to me would be a way, perhaps with an option in initdb, to
> just say, initialize this cluster compatibly with that other cluster, so
> you don't have to worry about these details.
Good idea, though I'd think of it as a pg_upgrade option more than being
initdb's problem. Either way, though, it would be on the code's head
to do something about converting the postgresql.conf, pg_hba.conf, etc
configuration files from the old cluster to the new, which means this
isn't just a trivial matter of running initdb on the target PGDATA
location. That turns it into a bit of a research project I'm afraid
--- but if we could get there, it'd be a nice improvement.
regards, tom lane
В списке pgsql-hackers по дате отправления: