On Mar 6, 2009, at 11:10 AM, Tom Lane wrote:
Carol Walter writes:
Well, it seems like that could happen. This is a machine that has a
instance of 8.2 running on it. My bash history says that the command
that I ran to start the 8.3.6 instance is
pg_ctl start -D /db02/postgres/data8.3.6/data
Carol Walter writes:
> Well, it seems like that could happen. This is a machine that has a
> instance of 8.2 running on it. My bash history says that the command
> that I ran to start the 8.3.6 instance is
> pg_ctl start -D /db02/postgres/data8.3.6/data -l data836.log. /db02/
> postgres/da
On Mar 6, 2009, at 10:37 AM, Tom Lane wrote:
Carol Walter writes:
I am building a test instance of PosgreSQL 8.3.6 on a Solaris 10 box.
When start the server, if fails to start. In the log there are these
statements...
-bash-3.00$ more data836.log
FATAL: unrecognized configuration parame
Carol Walter writes:
> I am building a test instance of PosgreSQL 8.3.6 on a Solaris 10 box.
> When start the server, if fails to start. In the log there are these
> statements...
> -bash-3.00$ more data836.log
> FATAL: unrecognized configuration parameter
> "default_text_search_config"
Hello,
I am building a test instance of PosgreSQL 8.3.6 on a Solaris 10 box.
When start the server, if fails to start. In the log there are these
statements...
-bash-3.00$ more data836.log
FATAL: unrecognized configuration parameter
"default_text_search_config"
FATAL: unrecognized con
