Thread: Editing contrib modules which are loaded by default?
In all of postgres 8.1.4 (windows) databases I create there are a bunch of cube and g_cube functions added to the db. If these are not needed, is there a simple way to make sure that they are not added to new databases? -- View this message in context: http://www.nabble.com/Editing-contrib-modules-which-are-loaded-by-default--tf2705139.html#a7542807 Sent from the PostgreSQL - general mailing list archive at Nabble.com.
On 25 Nov 2006 at 14:24, novnov wrote: > In all of postgres 8.1.4 (windows) databases I create there are a > bunch of cube and g_cube functions added to the db. If these are not > needed, is there a simple way to make sure that they are not added to > new databases? As I was telling you on the pgadmin-support list, these are copied from the template1 database whenever you create a new database - the CREATE DATABASE command effectively duplicates template1. To prevent these functions from appearing in your new databases, remove them from template1. Have a look at the docs: http://www.postgresql.org/docs/8.1/interactive/manage-ag- createdb.html --Ray O'Donnell ---------------------------------------------------------------------- Raymond O'Donnell Director of Music, Galway Cathedral, Galway, Ireland rod@iol.ie ----------------------------------------------------------------------
Hi Ray - yes I read and checked in to your advice on the other list but I posted here because the procedure looked a little complex and possibly risky for a newbie like me. Rather than ask you for a simpler way to go, I figured I'd post here and see what I came up with...and knew of course that you'd probably be on this list too. I'm just hoping that there is a way to clear those spurious (to me) entries without the level of hacking that the article you pointed me to entailed. Raymond O wrote: > > On 25 Nov 2006 at 14:24, novnov wrote: > >> In all of postgres 8.1.4 (windows) databases I create there are a >> bunch of cube and g_cube functions added to the db. If these are not >> needed, is there a simple way to make sure that they are not added to >> new databases? > > As I was telling you on the pgadmin-support list, these are copied > from the template1 database whenever you create a new database - the > CREATE DATABASE command effectively duplicates template1. > > To prevent these functions from appearing in your new databases, > remove them from template1. > > Have a look at the docs: > http://www.postgresql.org/docs/8.1/interactive/manage-ag- > createdb.html > > --Ray O'Donnell > > ---------------------------------------------------------------------- > > Raymond O'Donnell > Director of Music, Galway Cathedral, Galway, Ireland > rod@iol.ie > ---------------------------------------------------------------------- > > > > ---------------------------(end of broadcast)--------------------------- > TIP 1: if posting/reading through Usenet, please send an appropriate > subscribe-nomail command to majordomo@postgresql.org so that your > message can get through to the mailing list cleanly > > -- View this message in context: http://www.nabble.com/Editing-contrib-modules-which-are-loaded-by-default--tf2705139.html#a7542987 Sent from the PostgreSQL - general mailing list archive at Nabble.com.
I hadn't checked and the page you pointed to here was different from the one you pointed to on the other list (http://www.postgresql.org/docs/techdocs.22). I've experimented a bit and have been able to see what template0 consists of by creating a db based on it. It lacks the ref to the lang plpgsql. So if I made a new template1 from template0, all new dbs would lack that lang. That leaves me with a different starting point for my new dbs but still not what I want. Seems like this core config aspect of postgres could be a little simpler to manage...anyways I'll figure it out, your pointers have helped. novnov wrote: > > Hi Ray - yes I read and checked in to your advice on the other list but I > posted here because the procedure looked a little complex and possibly > risky for a newbie like me. Rather than ask you for a simpler way to go, I > figured I'd post here and see what I came up with...and knew of course > that you'd probably be on this list too. I'm just hoping that there is a > way to clear those spurious (to me) entries without the level of hacking > that the article you pointed me to entailed. > > > > Raymond O wrote: >> >> On 25 Nov 2006 at 14:24, novnov wrote: >> >>> In all of postgres 8.1.4 (windows) databases I create there are a >>> bunch of cube and g_cube functions added to the db. If these are not >>> needed, is there a simple way to make sure that they are not added to >>> new databases? >> >> As I was telling you on the pgadmin-support list, these are copied >> from the template1 database whenever you create a new database - the >> CREATE DATABASE command effectively duplicates template1. >> >> To prevent these functions from appearing in your new databases, >> remove them from template1. >> >> Have a look at the docs: >> http://www.postgresql.org/docs/8.1/interactive/manage-ag- >> createdb.html >> >> --Ray O'Donnell >> >> ---------------------------------------------------------------------- >> >> Raymond O'Donnell >> Director of Music, Galway Cathedral, Galway, Ireland >> rod@iol.ie >> ---------------------------------------------------------------------- >> >> >> >> ---------------------------(end of broadcast)--------------------------- >> TIP 1: if posting/reading through Usenet, please send an appropriate >> subscribe-nomail command to majordomo@postgresql.org so that your >> message can get through to the mailing list cleanly >> >> > > -- View this message in context: http://www.nabble.com/Editing-contrib-modules-which-are-loaded-by-default--tf2705139.html#a7543210 Sent from the PostgreSQL - general mailing list archive at Nabble.com.
Isn't there an option when you install on windows that controls what contrib stuff is included? Anyway, it's pretty simple to add plpgsql back in using CREATE LANGUAGE. On Nov 25, 2006, at 5:16 PM, novnov wrote: > > I hadn't checked and the page you pointed to here was different > from the one > you pointed to on the other list > (http://www.postgresql.org/docs/techdocs.22). I've experimented a > bit and > have been able to see what template0 consists of by creating a db > based on > it. It lacks the ref to the lang plpgsql. So if I made a new > template1 from > template0, all new dbs would lack that lang. That leaves me with a > different > starting point for my new dbs but still not what I want. > > Seems like this core config aspect of postgres could be a little > simpler to > manage...anyways I'll figure it out, your pointers have helped. > > > > novnov wrote: >> >> Hi Ray - yes I read and checked in to your advice on the other >> list but I >> posted here because the procedure looked a little complex and >> possibly >> risky for a newbie like me. Rather than ask you for a simpler way >> to go, I >> figured I'd post here and see what I came up with...and knew of >> course >> that you'd probably be on this list too. I'm just hoping that >> there is a >> way to clear those spurious (to me) entries without the level of >> hacking >> that the article you pointed me to entailed. >> >> >> >> Raymond O wrote: >>> >>> On 25 Nov 2006 at 14:24, novnov wrote: >>> >>>> In all of postgres 8.1.4 (windows) databases I create there are a >>>> bunch of cube and g_cube functions added to the db. If these are >>>> not >>>> needed, is there a simple way to make sure that they are not >>>> added to >>>> new databases? >>> >>> As I was telling you on the pgadmin-support list, these are copied >>> from the template1 database whenever you create a new database - the >>> CREATE DATABASE command effectively duplicates template1. >>> >>> To prevent these functions from appearing in your new databases, >>> remove them from template1. >>> >>> Have a look at the docs: >>> http://www.postgresql.org/docs/8.1/interactive/manage-ag- >>> createdb.html >>> >>> --Ray O'Donnell >>> >>> -------------------------------------------------------------------- >>> -- >>> >>> Raymond O'Donnell >>> Director of Music, Galway Cathedral, Galway, Ireland >>> rod@iol.ie >>> -------------------------------------------------------------------- >>> -- >>> >>> >>> >>> ---------------------------(end of >>> broadcast)--------------------------- >>> TIP 1: if posting/reading through Usenet, please send an appropriate >>> subscribe-nomail command to majordomo@postgresql.org so >>> that your >>> message can get through to the mailing list cleanly >>> >>> >> >> > > -- > View this message in context: http://www.nabble.com/Editing-contrib- > modules-which-are-loaded-by-default--tf2705139.html#a7543210 > Sent from the PostgreSQL - general mailing list archive at Nabble.com. > > > ---------------------------(end of > broadcast)--------------------------- > TIP 1: if posting/reading through Usenet, please send an appropriate > subscribe-nomail command to majordomo@postgresql.org so that > your > message can get through to the mailing list cleanly > -- Jim Nasby jim@nasby.net EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
I imagine that there is a step in the windows install that allows one to select contrib modules. I don't recall. I didn't add these contrib modules, so they must be included by default, which frankly seems pretty dumb. I've tried to follow the instructions on the pgsql site for replacing template1 with template0. It gets pretty complicated, because you can't delete a template db, so you have to convert it to a non-template, then delete, then proceed with the replacement. So, I did all of that and as far as I could tell all steps succeded. But a new db still contains all of the unwanted functions and types. I will resort to ininstalling pgsql and reinstalling. I have to say that this aspect of pgsql is rather difficult to work with. Starting with why cube and g_cube modules are included by default and ending with the difficulty of manipulating template1...it could be easier for newbies. I'll make a request on the pgAdmin list to see if these kinds of settings can't be somehow included in that tool. Jim Nasby-2 wrote: > > Isn't there an option when you install on windows that controls what > contrib stuff is included? > > Anyway, it's pretty simple to add plpgsql back in using CREATE LANGUAGE. > > On Nov 25, 2006, at 5:16 PM, novnov wrote: > >> >> I hadn't checked and the page you pointed to here was different >> from the one >> you pointed to on the other list >> (http://www.postgresql.org/docs/techdocs.22). I've experimented a >> bit and >> have been able to see what template0 consists of by creating a db >> based on >> it. It lacks the ref to the lang plpgsql. So if I made a new >> template1 from >> template0, all new dbs would lack that lang. That leaves me with a >> different >> starting point for my new dbs but still not what I want. >> >> Seems like this core config aspect of postgres could be a little >> simpler to >> manage...anyways I'll figure it out, your pointers have helped. >> >> >> >> novnov wrote: >>> >>> Hi Ray - yes I read and checked in to your advice on the other >>> list but I >>> posted here because the procedure looked a little complex and >>> possibly >>> risky for a newbie like me. Rather than ask you for a simpler way >>> to go, I >>> figured I'd post here and see what I came up with...and knew of >>> course >>> that you'd probably be on this list too. I'm just hoping that >>> there is a >>> way to clear those spurious (to me) entries without the level of >>> hacking >>> that the article you pointed me to entailed. >>> >>> >>> >>> Raymond O wrote: >>>> >>>> On 25 Nov 2006 at 14:24, novnov wrote: >>>> >>>>> In all of postgres 8.1.4 (windows) databases I create there are a >>>>> bunch of cube and g_cube functions added to the db. If these are >>>>> not >>>>> needed, is there a simple way to make sure that they are not >>>>> added to >>>>> new databases? >>>> >>>> As I was telling you on the pgadmin-support list, these are copied >>>> from the template1 database whenever you create a new database - the >>>> CREATE DATABASE command effectively duplicates template1. >>>> >>>> To prevent these functions from appearing in your new databases, >>>> remove them from template1. >>>> >>>> Have a look at the docs: >>>> http://www.postgresql.org/docs/8.1/interactive/manage-ag- >>>> createdb.html >>>> >>>> --Ray O'Donnell >>>> >>>> -------------------------------------------------------------------- >>>> -- >>>> >>>> Raymond O'Donnell >>>> Director of Music, Galway Cathedral, Galway, Ireland >>>> rod@iol.ie >>>> -------------------------------------------------------------------- >>>> -- >>>> >>>> >>>> >>>> ---------------------------(end of >>>> broadcast)--------------------------- >>>> TIP 1: if posting/reading through Usenet, please send an appropriate >>>> subscribe-nomail command to majordomo@postgresql.org so >>>> that your >>>> message can get through to the mailing list cleanly >>>> >>>> >>> >>> >> >> -- >> View this message in context: http://www.nabble.com/Editing-contrib- >> modules-which-are-loaded-by-default--tf2705139.html#a7543210 >> Sent from the PostgreSQL - general mailing list archive at Nabble.com. >> >> >> ---------------------------(end of >> broadcast)--------------------------- >> TIP 1: if posting/reading through Usenet, please send an appropriate >> subscribe-nomail command to majordomo@postgresql.org so that >> your >> message can get through to the mailing list cleanly >> > > -- > Jim Nasby jim@nasby.net > EnterpriseDB http://enterprisedb.com 512.569.9461 (cell) > > > > ---------------------------(end of broadcast)--------------------------- > TIP 3: Have you checked our extensive FAQ? > > http://www.postgresql.org/docs/faq > > -- View this message in context: http://www.nabble.com/Editing-contrib-modules-which-are-loaded-by-default--tf2705139.html#a7583745 Sent from the PostgreSQL - general mailing list archive at Nabble.com.
On Tue, 2006-11-28 at 09:38 -0800, novnov wrote:
> I imagine that there is a step in the windows install that allows one to
> select contrib modules. I don't recall. I didn't add these contrib modules,
> so they must be included by default, which frankly seems pretty dumb.
>
> I've tried to follow the instructions on the pgsql site for replacing
> template1 with template0. It gets pretty complicated, because you can't
> delete a template db, so you have to convert it to a non-template, then
> delete, then proceed with the replacement. So, I did all of that and as far
> as I could tell all steps succeded. But a new db still contains all of the
> unwanted functions and types.
If your new db containted all of the unwanted functions, then you didn't
do *something* correctly.
>
> I will resort to ininstalling pgsql and reinstalling. I have to say that
> this aspect of pgsql is rather difficult to work with. Starting with why
> cube and g_cube modules are included by default and ending with the
> difficulty of manipulating template1...it could be easier for newbies. I'll
> make a request on the pgAdmin list to see if these kinds of settings can't
> be somehow included in that tool.
There are uninstall scripts for all contrib modules that you could have
used.
Sincerely,
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
I'm sure I didn't do something properly but the point is, as a newbie, none of it is obvious. However I'm going to have to try again, as the setup for pgsql 8.1 does not seem to have a way to turn off the cube contrib modules. They are not listed anywhere in the setup console. Or I will try to find and execute the contrib module uninstall scripts. It's all a lot of work. Joshua D. Drake wrote: > > On Tue, 2006-11-28 at 09:38 -0800, novnov wrote: >> I imagine that there is a step in the windows install that allows one to >> select contrib modules. I don't recall. I didn't add these contrib >> modules, >> so they must be included by default, which frankly seems pretty dumb. >> >> I've tried to follow the instructions on the pgsql site for replacing >> template1 with template0. It gets pretty complicated, because you can't >> delete a template db, so you have to convert it to a non-template, then >> delete, then proceed with the replacement. So, I did all of that and as >> far >> as I could tell all steps succeded. But a new db still contains all of >> the >> unwanted functions and types. > > If your new db containted all of the unwanted functions, then you didn't > do *something* correctly. > >> >> I will resort to ininstalling pgsql and reinstalling. I have to say that >> this aspect of pgsql is rather difficult to work with. Starting with why >> cube and g_cube modules are included by default and ending with the >> difficulty of manipulating template1...it could be easier for newbies. >> I'll >> make a request on the pgAdmin list to see if these kinds of settings >> can't >> be somehow included in that tool. > > There are uninstall scripts for all contrib modules that you could have > used. > > Sincerely, > > Joshua D. Drake > > -- > > === The PostgreSQL Company: Command Prompt, Inc. === > Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240 > Providing the most comprehensive PostgreSQL solutions since 1997 > http://www.commandprompt.com/ > > Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate > > > > > ---------------------------(end of broadcast)--------------------------- > TIP 3: Have you checked our extensive FAQ? > > http://www.postgresql.org/docs/faq > > -- View this message in context: http://www.nabble.com/Editing-contrib-modules-which-are-loaded-by-default--tf2705139.html#a7584226 Sent from the PostgreSQL - general mailing list archive at Nabble.com.
On 28 Nov 2006 at 10:01, novnov wrote: > I'm sure I didn't do something properly but the point is, as a newbie, > none of it is obvious. The documentation that comes with PostgreSQL head-and-shoulders above anything that comes with many commercial products. If you're going to work woth PostgreSQL, it's a good idea to read as much of it as you can. > It's all a lot of work. But it's worth it..... :) ---------------------------------------------------------------------- Raymond O'Donnell Director of Music, Galway Cathedral, Galway, Ireland rod@iol.ie ----------------------------------------------------------------------
novnov wrote: > I'm sure I didn't do something properly but the point is, as a newbie, none > of it is obvious. > > However I'm going to have to try again, as the setup for pgsql 8.1 does not > seem to have a way to turn off the cube contrib modules. They are not listed > anywhere in the setup console. What do you mean by "setup console"? Because I just don't believe that the installer doesn't let you turn the cube contrib off. -- Richard Huxton Archonet Ltd
> ------- Original Message ------- > From: Richard Huxton <dev@archonet.com> > To: novnov <novnovice@gmail.com> > Sent: 28/11/06, 18:56:37 > Subject: Re: [GENERAL] Editing contrib modules which are loaded by default? > > Because I just don't believe that > the installer doesn't let you turn the cube contrib off. It does - in fact it's off by default. The libs & scripts are always installed with the server, but only loaded into template1if the user checks the appropriate box. Regards, Dave
I was wrong from the get-go, I apparently selected the cube contrib, because on reinstall it's not automatically selected, at least in 8.1.5. Richard Huxton wrote: > > novnov wrote: >> I'm sure I didn't do something properly but the point is, as a newbie, >> none >> of it is obvious. >> >> However I'm going to have to try again, as the setup for pgsql 8.1 does >> not >> seem to have a way to turn off the cube contrib modules. They are not >> listed >> anywhere in the setup console. > > What do you mean by "setup console"? Because I just don't believe that > the installer doesn't let you turn the cube contrib off. > > -- > Richard Huxton > Archonet Ltd > > ---------------------------(end of broadcast)--------------------------- > TIP 5: don't forget to increase your free space map settings > > -- View this message in context: http://www.nabble.com/Editing-contrib-modules-which-are-loaded-by-default--tf2705139.html#a7588330 Sent from the PostgreSQL - general mailing list archive at Nabble.com.