[GENERAL] recatalog existing databases after re-build from source

2009-03-13 Thread gnuoytr
Going through the PLPython threads on the Planet, I realized that I needed plpython. So I rebuilt PG with python, expecting that I could then re-catalog the databases. But, not. initdb, wants the data directory, which is where the database files are, and doesn't run if it's not empty. The

Re: [GENERAL] recatalog existing databases after re-build from source

2009-03-13 Thread Joshua D. Drake
On Fri, 2009-03-13 at 15:28 -0400, gnuo...@rcn.com wrote: Going through the PLPython threads on the Planet, I realied that I needed plpython. So I rebuilt PG with python, expecting that I could then re-catalog the databases. But, not. initdb, wants the data directory, which is where the

Re: [GENERAL] recatalog existing databases after re-build from source

2009-03-13 Thread Adrian Klaver
- Joshua D. Drake j...@commandprompt.com wrote: On Fri, 2009-03-13 at 15:28 -0400, gnuo...@rcn.com wrote: Going through the PLPython threads on the Planet, I realied that I needed plpython. So I rebuilt PG with python, expecting that I could then re-catalog the databases. But, not.

Re: [GENERAL] recatalog existing databases after re-build from source

2009-03-13 Thread Tom Lane
Adrian Klaver akla...@comcast.net writes: My guess is he thought he needed to re-initdb the cluster after rebuilding the source to generate plpythonu. Robert, you don't need to do that. At least, not as long as it's the same major PG version and you didn't change any configure options that