Re: WIP patch: Collation support

<div dir="ltr">Ok, so do you suggest to leave it with a notice "reindex database" or start to solve it somehow?<br
/><br/>Regards<br /><br />Radek Strnad<br /><br /><div class="gmail_quote">On Mon, Sep 1, 2008 at 12:08 AM, Alvaro
Herrera<span dir="ltr"><<a href="mailto:alvherre@commandprompt.com">alvherre@commandprompt.com</a>></span>
wrote:<br/><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex;
padding-left:1ex;">Radek Strnad escribió:<br /><div class="Ih2E3d"><br /> > - when creating database with different
collationthan database cluster, the<br /> > database has to be reindexed. Any idea how to do it? Function<br /> >
ReindexDatabaseworks only when database is opened.<br /><br /></div>We have this Todo item:<br /><br />  Set proper
permissionson non-system schemas during db creation<br />    Currently all schemas are owned by the super-user because
theyare<br />    copied from the template1 database. However, since all objects are<br />    inherited from the
templatedatabase, it is not clear that setting<br />    schemas to the db owner is correct.<br /><br /> When this was
discussedyears ago, one proposed idea was that on the<br /> first connection the backend should, as a first task,
ensurethat<br /> certain administrative chores be done.  The first of those was changing<br /> the ownership of
schemas. It sounds like this reindexing you propose<br /> falls into the same category.<br /><font color="#888888"><br
/>--<br /> Alvaro Herrera                                <a href="http://www.CommandPrompt.com/"
target="_blank">http://www.CommandPrompt.com/</a><br/> PostgreSQL Replication, Consulting, Custom Development, 24x7
support<br/></font></blockquote></div><br /></div>