Re: [GENERAL] Allowing multiple versions of PG under NetBSD

2016-07-29 Thread Thomas Munro
On Sat, Jul 30, 2016 at 8:51 AM, Stephen Frost wrote: > * Larry Rosenman (l...@lerctr.org) wrote: >> On 2016-07-29 15:14, Bruce Momjian wrote: >> >On Fri, Jul 29, 2016 at 03:09:59PM -0500, Larry Rosenman wrote: >> >>>Data Directory naming, as well as keeping the init-scripts

Re: [GENERAL] Allowing multiple versions of PG under NetBSD

2016-07-29 Thread Stephen Frost
* Larry Rosenman (l...@lerctr.org) wrote: > On 2016-07-29 15:14, Bruce Momjian wrote: > >On Fri, Jul 29, 2016 at 03:09:59PM -0500, Larry Rosenman wrote: > >>>Data Directory naming, as well as keeping the init-scripts straight. > >>> > >>And who gets 5432, and Unix socket naming, it starts to get

Re: [GENERAL] Allowing multiple versions of PG under NetBSD

2016-07-29 Thread Kevin Grittner
On Fri, Jul 29, 2016 at 3:22 PM, Larry Rosenman wrote: > I'm willing to help on the FreeBSD side. One more tip -- if you are running multiple clusters (same version or not) on the same machine, it is best to run each cluster under a separate OS user. It's not *required*, but

Re: [GENERAL] Allowing multiple versions of PG under NetBSD

2016-07-29 Thread Adrian Klaver
On 07/29/2016 01:17 PM, D'Arcy J.M. Cain wrote: On Fri, 29 Jul 2016 15:09:59 -0500 Larry Rosenman wrote: version to the bare version of the binary name. Example: - psql.8.3 - psql.9.1 - psql.9.3 - psql ==> psql.9.3 Other than linking to the correct library can you think

Re: [GENERAL] Allowing multiple versions of PG under NetBSD

2016-07-29 Thread Larry Rosenman
On 2016-07-29 15:17, D'Arcy J.M. Cain wrote: On Fri, 29 Jul 2016 15:09:59 -0500 Larry Rosenman wrote: >> version to the bare version of the binary name. Example: >> - psql.8.3 >> - psql.9.1 >> - psql.9.3 >> - psql ==> psql.9.3 >> >> Other than linking to the correct

Re: [GENERAL] Allowing multiple versions of PG under NetBSD

2016-07-29 Thread D'Arcy J.M. Cain
On Fri, 29 Jul 2016 15:09:59 -0500 Larry Rosenman wrote: > >> version to the bare version of the binary name. Example: > >> - psql.8.3 > >> - psql.9.1 > >> - psql.9.3 > >> - psql ==> psql.9.3 > >> > >> Other than linking to the correct library can you think of any > >>

Re: [GENERAL] Allowing multiple versions of PG under NetBSD

2016-07-29 Thread Larry Rosenman
On 2016-07-29 15:14, Bruce Momjian wrote: On Fri, Jul 29, 2016 at 03:09:59PM -0500, Larry Rosenman wrote: >>I might take a look at the NetBSD package (I'm a developer) to see how >>hard it would be to allow multiple versions. We do keep all the lib >>stuff in a separate directory so that part

Re: [GENERAL] Allowing multiple versions of PG under NetBSD

2016-07-29 Thread Bruce Momjian
On Fri, Jul 29, 2016 at 03:09:59PM -0500, Larry Rosenman wrote: > >>I might take a look at the NetBSD package (I'm a developer) to see how > >>hard it would be to allow multiple versions. We do keep all the lib > >>stuff in a separate directory so that part would be relatively simple. > >>We just

Re: [GENERAL] Allowing multiple versions of PG under NetBSD

2016-07-29 Thread Larry Rosenman
On 2016-07-29 15:06, Larry Rosenman wrote: On 2016-07-29 15:04, D'Arcy J.M. Cain wrote: On Fri, 29 Jul 2016 15:07:53 -0400 Bruce Momjian wrote: > The answer is either chroot or mount and run pg_upgrade on another > server. If you can afford the downtime you can also delete

Re: [GENERAL] Allowing multiple versions of PG under NetBSD

2016-07-29 Thread Larry Rosenman
On 2016-07-29 15:04, D'Arcy J.M. Cain wrote: On Fri, 29 Jul 2016 15:07:53 -0400 Bruce Momjian wrote: > The answer is either chroot or mount and run pg_upgrade on another > server. If you can afford the downtime you can also delete PG, > install the new version and run

Re: [GENERAL] Allowing multiple versions of PG under NetBSD

2016-07-29 Thread D'Arcy J.M. Cain
On Fri, 29 Jul 2016 15:07:53 -0400 Bruce Momjian wrote: > > The answer is either chroot or mount and run pg_upgrade on another > > server. If you can afford the downtime you can also delete PG, > > install the new version and run pg_upgrade without modifying the > > existing DB.