This forum has been archived. All content is frozen. Please use KDE Discuss instead.

Postgres corruption or confusion

Tags: None
(comma "," separated)
purloiner
Registered Member
Posts
13
Karma
0

Postgres corruption or confusion

Wed Nov 29, 2006 11:17 am
Hi all

I'm having problems with postgres although the problem may be my misunderstanding I'm sure its a bug, whichever it is driving me nuts because I just love Amarok.

I have a central server holding my collection and running the postgres server on gentoo postgresql-8.0.8.  The collection is via an nfs mount.  I have multiple clients all running gentoo; amarok is compiled from source rather than the gentoo ebuild.  Built with ./configure --enable-postgresql

Most of the clients are 11b wireless so have watch folder scanning disabled because it gobbles too much bandwidth.  One client is wired and has watch folder scanning enabled to keep the database up to date.  The clients all use the same login to the database (uname/passwd)  Sometimes the database on all the wireless clients is opened but has nothing in it  :confused:  If I manually rescan the collection on one of the clients, that client has a valid but new database, the other clients don't see this database so I lose my statistics and ratings etc.  Other times it works even after the wired client has rescanned the collection and found new music, then suddenly I lose consistency.

So I drop the database in postgres and restore it from the previously fully working backup (tried pg_dump and pg_dumpall) now I find the client that originally created the database has full access and all the stats are intact but the other clients again see an empty database.  There are other problems were I will sometimes find 2 machines see 1 database and a 3rd machine sees a different one.

I'm completely baffled, I'm not a linux or database expert, this used to work fine I'm sure, I'm now backing up step by step down the patch release to find where it got broken.  Any help would be appreciated  :confused: :confused:
User avatar
dangle_wtf
Moderator
Posts
1252
Karma
0
This is possibly the same bug someone else was experiencing with a shared mysql db, that's only occured since the introduction of dynamic collections. I haven't seen any followup on that thread,

You should either mail the devel mailing list (amarok@kde.org) with this information and question, and/or post a bug report at http://bugs.kde.org


"There are two theories to arguing with women. Neither one works."
.
If men could get pregnant, we'd learn the true meaning of "screaming nancyboy wuss"
User avatar
dangle_wtf
Moderator
Posts
1252
Karma
0


"There are two theories to arguing with women. Neither one works."
.
If men could get pregnant, we'd learn the true meaning of "screaming nancyboy wuss"
purloiner
Registered Member
Posts
13
Karma
0
I'll try to disable dynamic collections and rebuild the database and let you know, thanks dangle
purloiner
Registered Member
Posts
13
Karma
0
Dangle, thanks that has fixed it, tbh I don't understand why but it is working  :cool: :cool: :biggrin:


Bookmarks



Who is online

Registered users: Bing [Bot], Google [Bot], kde-naveen, Sogou [Bot], Yahoo [Bot]