| From: | Teodor Sigaev <teodor(at)sigaev(dot)ru> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Proposal: syntax of operation with tsearch's configuration |
| Date: | 2006-11-17 18:09:34 |
| Message-ID: | 455DFADE.7050409@sigaev.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hmm, IMHO, it's needed for consistent interface: nobody adds new column to table
by editing pg_class & pg_attribute, nobody looks for description of table by
selection values from system table.
Tom Lane wrote:
> Teodor Sigaev <teodor(at)sigaev(dot)ru> writes:
>> Now we (Oleg and me) are working on moving tsearch into core.
>> Pls, review suggested syntax. Comments, suggestions, objections will be appreciated.
>
> Is it really necessary to invent a batch of special-purpose commands?
> Seems like this will add some thousands of lines of code and no actual
> new functionality; not to mention loss of backwards compatibility for
> existing tsearch2 users.
>
> regards, tom lane
--
Teodor Sigaev E-mail: teodor(at)sigaev(dot)ru
WWW: http://www.sigaev.ru/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2006-11-17 18:43:04 | Re: Proposal: syntax of operation with tsearch's configuration |
| Previous Message | Tom Lane | 2006-11-17 17:12:47 | Re: Proposal: syntax of operation with tsearch's configuration |