Hello!
I am currently having a recurring Locking problem on my Postgres 9.0.4
Database. I had the same Problem on 9.0.1 and updated to 9.0.4 then.
It worked fine for a while and just resurfaced.
Suddenly it seems as though there is some kind of "deadlock" in the
database, which prevents my client
Hi Scott,
SM> Snip. Those are ALL either AccessShareLock (which is very low level
SM> and non-blocking) or virtual tx locks, which again don't block
SM> anything but their own transaction. Nothing there screams "locks!"
SM> for a better view of locks and how they're blocking things you can use
S
Hello,
the problem just resurfaced and the Wiki page dows not really help
very much.
When i look into the pg_stat_activity, i only see that the connections
all state " in transaction".
Is there any way to find out what the transaction is doing exactly to
be able to debug the Problem?
Best regar
Hi!
I have a problem migrating my Database using TSearch2 with the UTF-8
Backport from 8.1.3 to a new database with 8.2.0.
I successfully installed postgres and the TSearch2 distributed with
it and copied the german.aff/german.med/german.stop and
german.stop.ispell from my old postgre
Hi,
TS> Send to me dict and aff file, pls
see attached .aff file, I have not created the file from a dict
myself but taken the .aff/.med/.stop/.stop.ispell from this blog:
http://www.tauceti.net/roller/cetixx/category/Tipps ...
TS> By the way, tsearch2 is changed significantly, so, the better w
thanks, that fixed it :-)
Best regards
Manuel
TS> Affix file has artifact:
TS> PFX G N 1
TS> .> GE
TS> which is strange mix of openoffice format and ispell format. Just remove
they.
TS> 8.2 Ispell code checks format strongly that in previous versions, even
backported :)
--
Hi!
I am having a tsearch2 problem on postgres 8.2 again ...
when I try to set the default config for tsearch2 with
"select set_curcfg('default'); it works fine in the same pgadmin
session when i use "select show_curcfg();" afterwards. The correct
OID is shown.
If i then close
PM, you wrote:
HD> I think the best way is to adjust the locale for your default config:
HD> Type:
HD> SHOW lc_ctype; (or some other lc_* variables) in psql.
HD> to find your cluster locale, then:
HD> UPDATE
HD>public.pg_ts_cfg
HD> SET
HD>locale = ''