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 suceeded. But a new db still contains all of the
unwanted functions and types. So I was not successful after all.
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.
Would it be possible in a future release of pgAdmin that access to these
settings can be adjusted?
Raymond O wrote:
>
> On 22 Nov 2006 at 17:21, novnov wrote:
>
>> Not sure this is a pgAdmin question either but why does pg seem to
>> create a mass of cube and g_cube functions for each new db? They sure
>> clutter up the place, but maybe they are needed by postgres?
>
> It soundsas if one of the contrib modules may be loaded by default -
> new DBs are created by copying the template1 database, so anything
> that's in template1 is included in new databases also.
>
> There is a procedure, if you don't want this or if you load a heap of
> stuff into template1 by accident, for zapping template1 and re-
> creating it in turn from template0 - it's detailed at
> http://www.postgresql.org/docs/techdocs.22
>
> --Ray.
>
>
> ----------------------------------------------------------------------
>
> Raymond O'Donnell
> Director of Music, Galway Cathedral, Galway, Ireland
> rod@iol.ie
> ----------------------------------------------------------------------
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster
>
>
--
View this message in context:
http://www.nabble.com/Newbie-questions%2C-diff-between-functions-and-procedures----why-cube-functions--tf2689810.html#a7583884
Sent from the PostgreSQL - pgadmin support mailing list archive at Nabble.com.