| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM> |
| Cc: | Gregory Stark <stark(at)enterprisedb(dot)com>, 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:35:11 |
| Message-ID: | 20080916153511.GG9229@alvh.no-ip.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Zdenek Kotala escribió:
> Gregory Stark napsal(a):
>> 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.
It's only supposed to work if you're not previously connected to any
database. (Autovacuum never "switches to another database"; any
particular worker only connects to a single database).
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sushant Sinha | 2008-09-16 16:00:06 | Re: text search patch status update? |
| Previous Message | Alvaro Herrera | 2008-09-16 15:27:09 | Re: text search patch status update? |