Re: Reconfiguring active PostgreSQL instance

Hi,

On Tue, Dec 21, 2021 at 01:42:41PM +0000, Reno, Natalie wrote:
> We provide a PostgreSQL instance that we configure ourselves.

Just saying, but this would not have been a problem if you had used the
RPM packages.

> An application is now needing the uuid-ossp extension which requires
> the -with-uuid=ossp flag added to the configuration. When we did the
> original configuration, we did the entire world which means the
> libraries are available.

I guess you mean you ran "make world"?

> Is there any way to add this to the configuration without having to
> re-run the make and installs? Or is there a way around this like
> copying the .sql and .lib files to the appropriate directories? Or can
> the configure statement be run again with just the new flag?

> Here is what we run for each install:
>
> ./configure --prefix=${POSTGRES_DIR} --bindir=${POSTGRES_DIR}/bin --sbindir=${POSTGRES_DIR}/sbin --libexecdir=${POSTGRES_DIR}/libexec --sysconfdir=${POSTGRES_DIR}/etc --libdir=${POSTGRES_DIR}/lib --includedir=${POSTGRES_DIR}/include --datadir=${POSTGRES_DIR}/data --mandir=${POSTGRES_DIR}/man --docdir=${POSTGRES_DIR}/doc --htmldir=${POSTGRES_DIR}/doc --dvidir=${POSTGRES_DIR}/doc --pdfdir=${POSTGRES_DIR}/doc --psdir=${POSTGRES_DIR}/doc --with-perl --with-systemd --with-pam

It /should/ work if you add --with-uuid=something to the above line,
rerun it and then change intro the contrib/uuid-ossp/ directory and run
"make" followed by "make install" from there. Then, "CREATE EXTENSION"
should work.

However, to be sure, I advise to make a backup of the full (built)
source tree beforehand and to try it on a test/development instance
first.

Which uuid library you prefer (and replace for "something" above) should
be something you can figure out yourself.

Michael