Re: WIP patch: Collation support
| От | Radek Strnad |
|---|---|
| Тема | Re: WIP patch: Collation support |
| Дата | |
| Msg-id | de5165440809010201q24129262v807adef65b613752@mail.gmail.com обсуждение |
| Ответ на | Re: WIP patch: Collation support (Alvaro Herrera <alvherre@commandprompt.com>) |
| Ответы |
Re: WIP patch: Collation support
|
| Список | pgsql-hackers |
Ok, so do you suggest to leave it with a notice "reindex database" or start to solve it somehow?
Regards
Radek Strnad
Regards
Radek Strnad
On Mon, Sep 1, 2008 at 12:08 AM, Alvaro Herrera <alvherre@commandprompt.com> wrote:
Radek Strnad escribió:We have this Todo item:
> - when creating database with different collation than database cluster, the
> database has to be reindexed. Any idea how to do it? Function
> ReindexDatabase works only when database is opened.
Set proper permissions on non-system schemas during db creation
Currently all schemas are owned by the super-user because they are
copied from the template1 database. However, since all objects are
inherited from the template database, it is not clear that setting
schemas to the db owner is correct.
When this was discussed years ago, one proposed idea was that on the
first connection the backend should, as a first task, ensure that
certain administrative chores be done. The first of those was changing
the ownership of schemas. It sounds like this reindexing you propose
falls into the same category.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
В списке pgsql-hackers по дате отправления: