Обсуждение: template1 database...

We have accidentally added tables and other objects to this database.

How do we return template1 back to the default setup?

Thomas LeBlanc

_________________________________________________________________
<b>Get MSN 8</b> and help protect your children with advanced parental
controls.  http://join.msn.com/?page=features/parental

Hi,

On Wed, 20 Aug 2003, Thomas LeBlanc wrote:

> We have accidentally added tables and other objects to this database.
>
> How do we return template1 back to the default setup?

I think this will help you:

http://techdocs.postgresql.org/techdocs/pgsqladventuresep1.php
Written by Josh Berkus.

Regards,
--
Devrim GUNDUZ
devrim@gunduz.org                devrim.gunduz@linux.org.tr
            http://www.tdmsoft.com
            http://www.gunduz.org

The link is very good. But another question.
In PostgreSQL, a superuser can modify almost everything in the
databases. But I don't think that should be the default. Maybe
adding an option is better. When a superuser want to change
something owned by the system, he or she can turn the option
on, then do what he want. After that, the option should be turned
back to off.

"Devrim GUNDUZ" <devrim@gunduz.org>
news:Pine.LNX.4.44.0308202243580.10233-100000@emo.org.tr...
>
> Hi,
>
> On Wed, 20 Aug 2003, Thomas LeBlanc wrote:
>
> > We have accidentally added tables and other objects to this database.
> >
> > How do we return template1 back to the default setup?
>
> I think this will help you:
>
> http://techdocs.postgresql.org/techdocs/pgsqladventuresep1.php
> Written by Josh Berkus.
>
> Regards,
> --
> Devrim GUNDUZ
> devrim@gunduz.org devrim.gunduz@linux.org.tr
> http://www.tdmsoft.com
> http://www.gunduz.org
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
>     (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
>

On Sun, Aug 24, 2003 at 00:38:35 +0800,
  Chris M <chris@none.none> wrote:
>
> The link is very good. But another question.
> In PostgreSQL, a superuser can modify almost everything in the
> databases. But I don't think that should be the default. Maybe
> adding an option is better. When a superuser want to change
> something owned by the system, he or she can turn the option
> on, then do what he want. After that, the option should be turned
> back to off.

This is usually accomplished by logging in as a normal user for most
tasks and only using a superuser account when it is needed.

"Bruno Wolff III" <bruno@wolff.to>>
> This is usually accomplished by logging in as a normal user for most
> tasks and only using a superuser account when it is needed.

Yes. DBAs should be careful when operating on the databases.

But I have seen many people using the superuser in MS SQL
Server to operate on the databases. Maybe that's why MS SQL
Server has an option to allow a superuser  change system
objects or not. That's why I think the option is useful for users,
especially those familar with MS Windows.