Re: How I changed the encoding of template1 after the fact

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Kevin Murphy <murphy(at)genome(dot)chop(dot)edu>
Cc: PostgreSQL general <pgsql-general(at)postgresql(dot)org>
Subject: Re: How I changed the encoding of template1 after the fact
Date: 2006-02-23 21:52:36
Message-ID: 26266.1140731556@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Kevin Murphy <murphy(at)genome(dot)chop(dot)edu> writes:
> Here's a condensed example, in which template1 is recreated to change
> its default encoding:

If you're willing to fool around at that level, why not just
"UPDATE pg_database SET datencoding = ..."

The restriction against dropping template databases is specifically
intended to make it difficult for those who don't know what they are
doing to shoot themselves in the foot. So I'm disinclined to make the
manual include easy-to-follow directions for bypassing the safety
interlock --- if you can't be bothered to find out how, you shouldn't
be doing it.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Jim C. Nasby 2006-02-23 22:21:19 Re: now() time off
Previous Message Bernhard Weisshuhn 2006-02-23 21:52:13 Re: Temporal Databases