Re: Tsearch2 update for Win32.

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "PostgreSQL-patches" <pgsql-patches(at)postgresql(dot)org>
Subject: Re: Tsearch2 update for Win32.
Date: 2004-09-08 14:24:01
Message-ID: E7F85A1B5FF8D44C8A1AF6885BC9A0E41A7A8A@ratbert.vale-housing.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

> -----Original Message-----
> From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
> Sent: 08 September 2004 15:14
> To: Dave Page
> Cc: PostgreSQL-patches
> Subject: Re: [PATCHES] Tsearch2 update for Win32.
>
> While I have no particular objection to adjusting the
> tsearch2 script, why has the installer got a problem with it?
> Seems like this suggests a bug in win32 psql.

The installer runs contrib module scripts without using psql - it
executes them in a 'custom action' - code that is added to the
installation package in this case as a dll. Adding copy support for one
contrib module is a headache I'd prefer to avoid :-)

> (I'm not sure
> why the installer would even be executing this script anyway ...)

It's a point and click (drool?) installer - it installs pg along with
pgAdmin and interfaces such as JDBC, Npgsql and psqlODBC, creates the
service user account, initdb's, installs any PLs and contrib modules the
user has selected. The user doesn't need to use psql at all if he
doesn't wish - which is exactly what most SQL Server/Windows users are
used to; no command line tools.

Regards, Dave.

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2004-09-08 14:28:08 Re: Tsearch2 update for Win32.
Previous Message Tom Lane 2004-09-08 14:14:18 Re: Tsearch2 update for Win32.