[SQL] [PERFORM] Can we activate WAL runtime?
Hi All, I am using postgres 8.2. I want to use Write Ahead Log (WAL) functionality to take a back up. I know one way to activate WAL is through updating postgres.conf file with archive_command. but how do I activate it on the server command line? Can we activate it runtime? Thanks in advance. - Prakash
[SQL] Re: [DOCS] Extending PostgreSQL Using C
On Wed, 7 Mar 2001, Tom Lane wrote: > Hannu Krosing <[EMAIL PROTECTED]> writes: > > Boulat Khakimov wrote: > >> ERROR: Can't find function encrypt in file /[full path here]/encrypt.so > > > Can _postgres_ user read /[full path here]/encrypt.so ? > > Presumably so. If he were unable to load the .so file, he'd be getting > a different error message. This message indicates that he got past the > load step, but dl_sym is unable to resolve the symbol "encrypt". > > I asked about the symbol names shown by nm(1), but got no answer ... It should be noted that encrypt() is a function already declared in unistd.h, which the OP is including. Could that be causing some problem since the OP is using the same name? Nishad -- "Underneath the concrete, the dream is still alive" -- Talking Heads ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
[SQL] Tsearch not searching 'Y'
Hello All,
I am trying to get tsearch working for my application but I am facing a
problem when alphabet 'Y' is the in the tsquery.
can anyone please share some light on it.
# SELECT 'hollywood'::tsvector @@ to_tsquery('holly:*');
?column?
--
f
(1 row)
SELECT 'hollywood'::tsvector @@ to_tsquery('holl:*');
?column?
--
t
(1 row)
It works when i put <> in y as below but i don't want to do it that way.
SELECT 'hollywood'::tsvector @@ to_tsquery('holl:*');
?column?
--
t
Thanks in advance
[SQL] Re: Re: [GENERAL] [SQL] Tsearch not searching 'Y'
On Thu, 29 Apr 2010 19:27:33 +0530 wrote
>On Thu, Apr 29, 2010 at 01:13:40PM -, sandeep prakash dhumale wrote:
>> Hello All,
>>
>> I am trying to get tsearch working for my application but I am facing a
>> problem when alphabet 'Y' is the in the tsquery.
>>
>> can anyone please share some light on it.
>>
>>
>> # SELECT 'hollywood'::tsvector @@ to_tsquery('holly:*');
>> ?column?
>> --
>> f
>> (1 row)
>>
>> SELECT 'hollywood'::tsvector @@ to_tsquery('holl:*');
>> ?column?
>> --
>> t
>> (1 row)
>>
>>
>> It works when i put <> in y as below but i don't want to do it
that way.
>>
>> SELECT 'hollywood'::tsvector @@ to_tsquery('holl<y>:*');
>> ?column?
>> --
>> t
>>
>> Thanks in advance
>
>That is because the to_tsquery() normalizes the tokens. Here is
>what I get from the default configuration:
>
>db=# select to_tsquery('holly:*');
> to_tsquery
>
> 'holli':*
>(1 row)
>
>db=# select to_tsquery('holl:*');
> to_tsquery
>
> 'holl':*
>(1 row)
>
>It is pretty easy to see why you see the behavior that you do.
>Maybe you need to change your tsearch configuration to match what
>you expect to happen.
>
>Regards,
>Ken
>
>
>--
>Sent via pgsql-general mailing list (pgsql-gene...@postgresql.org)
>To make changes to your subscription:
>http://www.postgresql.org/mailpref/pgsql-general
>
First of all thanks for your replies Tom and Ken,
I am little newbie to Tsearch so I appologies if I sound a little confuse.
Tom: If i do by casting like you wrote then i ran into case sensitivity issue
also then it does not work for other searches I guess then it sees for exact
matches and not normalize to lexims.
Ken: As you said I need to change my configuration, It would be great if you
can point me out where i can change that configuration
and what about that <y> in the query how does it work, does that
mean to explicitly include y in to_tsquery.
All your help is higly appriciated.
--Sandy
