On Sat, 2006-11-18 at 00:13 +0100, Martijn van Oosterhout wrote:
On Fri, Nov 17, 2006 at 03:53:35PM -0500, Tom Lane wrote:
Having the supporting code in core does not make much of a difference
otherwise from having it in contrib, does it?
Given the nonextensibility of gram.y and
On Sat, 18 Nov 2006, Simon Riggs wrote:
On Sat, 2006-11-18 at 00:13 +0100, Martijn van Oosterhout wrote:
On Fri, Nov 17, 2006 at 03:53:35PM -0500, Tom Lane wrote:
Having the supporting code in core does not make much of a difference
otherwise from having it in contrib, does it?
Given the
Oleg Bartunov wrote:
So, if we'll not touch grammar, are there any issues with tsearch2 in
core ?
Are there any issues with tsearch2 not in core?
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 3: Have
Hi,
Peter Eisentraut wrote:
Are there any issues with tsearch2 not in core?
I have run into troubles when restoring a dump, especially across
different versions of PostgreSQL and tsearch2. Mainly because pg_ts_*
are not system tables and thus need to be restored or installed separately.
On Sat, 18 Nov 2006, Andrew Dunstan wrote:
Peter Eisentraut wrote:
Oleg Bartunov wrote:
So, if we'll not touch grammar, are there any issues with tsearch2 in
core ?
Are there any issues with tsearch2 not in core?
Quite apart from anything else, it really needs documentation of the
