| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Yuri Niyazov <yuri(at)academia(dot)edu>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: pg_upgrade documentation improvement patch |
| Date: | 2016-04-13 13:50:09 |
| Message-ID: | 20453.1460555409@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Eisentraut <peter_e(at)gmx(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-04-13 13:52:04 | Re: Re: [COMMITTERS] pgsql: Avoid extra locks in GetSnapshotData if old_snapshot_threshold < |
| Previous Message | Robert Haas | 2016-04-13 13:47:03 | Re: SET ROLE and reserved roles |