| From: | Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM> |
|---|---|
| To: | Gregory Stark <stark(at)enterprisedb(dot)com> |
| Cc: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Martijn van Oosterhout <kleptog(at)svana(dot)org>, Radek Strnad <radek(dot)strnad(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: WIP patch: Collation support |
| Date: | 2008-09-16 15:00:13 |
| Message-ID: | 48CFC9FD.408@sun.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Gregory Stark napsal(a):
> Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> writes:
>
<snip>
> AFAIK we can't easily connect to the new database and do some fiddling with
> it, can we? If we could we could check if there are any non-empty indexes
> which depend on the collation and only print the warning if we find any (and
> even mark them invalid).
>
Autovacum uses InitPostgres function to swith to another database. I'm
not sure how much safe it is in create database command and when we are
already switched we can reindex affected indexes.
Zdenek
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zdenek Kotala | 2008-09-16 15:06:55 | Re: WIP patch: Collation support |
| Previous Message | Pavel Stehule | 2008-09-16 14:53:12 | Re: proposal - GROUPING SETS |