| From: | "Ian Barwick" <barwick(at)gmail(dot)com> |
|---|---|
| To: | "Mag Gam" <magawake(at)gmail(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: tsearch2 best practices |
| Date: | 2007-11-19 13:44:41 |
| Message-ID: | 1d581afe0711190544y783f9186h60c091cbc7186d6e@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
2007/11/18, Mag Gam <magawake(at)gmail(dot)com>:
> Hi All,
>
> Planning to implement tsearch2 for my websitem and dbschema. I wanted to
> know if there is a "Best practices" guide I should be following. While
> reading about it, I noticed there were lot of 'gotchas' with this, such as
> back-up/restore, Slony 1 replication issues, etc..
>
> What do most people recommend for backup/restore solution: 1) Install
> tsearch 2)Alter tables for tsearch2, update trigger, 3) do work .. 4)
> uninstall tsearch2, 5)backup? Is that the right approach? Or something else?
>
> Also, when will tsearch2 part of core, instead of contrib?
tsearch2 has been integrated into the upcoming 8.3 release (currently beta).
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mike Charnoky | 2007-11-19 14:01:52 | convert custom datatype to array |
| Previous Message | Tom Allison | 2007-11-19 13:26:20 | IP addresses |