Re: [ADMIN] Still a bug in the VACUUM ??? !!!
On Friday 14 February 2003 17:55, Tom Lane wrote: Andreas Schmitz [EMAIL PROTECTED] writes: I have a problem with the vacuum full. every time I run the vacuum command I loose data from the parent tables. maybe also from the subtables (haven't checked yet). I tried it a few times up to now an I can reproduce the phenomena. That sounds ugly ... but are you sure you don't have a hardware problem? I don't think anyone's ever reported such behavior before. If it is a Postgres bug, we can't do much to help you without a lot more detail. regards, tom lane hi, it does sound ugly. I checked the hardware. I can't see any problems with it. I know, somestimes you need a lot of luck to see a CPU problem under solaris. But I think the hardware is ok. however, what kind of details do you need to qualify if it's a postgres problem or not ? regards -andreas schmitz ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [ADMIN] Still a bug in the VACUUM ??? !!!
I have a problem with the vacuum full. every time I run the vacuum command I loose data from the parent tables. maybe also from the subtables (haven't checked yet). I tried it a few times up to now an I can reproduce the phenomena. That sounds ugly ... but are you sure you don't have a hardware problem? I don't think anyone's ever reported such behavior before. If it is a Postgres bug, we can't do much to help you without a lot more detail. regards, tom lane I have a similiar problem with VACUUM FULL ANALYZE. I do not loose any data, but get hundreds of uninitialized pages and a segmentation fault. Processing is very slow (twenty minutes). The only thing unusual about my configuration is that system indices are bloated. I expect the hardwhere to be ok, but I can not verify it because the sever is hosted elsewhere. The last lines of output were: NOTICE: Rel pg_class: Uninitialized page 3344 - fixing NOTICE: Rel pg_class: Uninitialized page 3345 - fixing NOTICE: Rel pg_class: Uninitialized page 3346 - fixing NOTICE: Rel pg_class: Uninitialized page 3347 - fixing NOTICE: Rel pg_class: Uninitialized page 3348 - fixing NOTICE: Rel pg_class: Uninitialized page 3349 - fixing NOTICE: Rel pg_class: Uninitialized page 3350 - fixing NOTICE: Rel pg_class: Uninitialized page 3351 - fixing NOTICE: Rel pg_class: Uninitialized page 3352 - fixing NOTICE: Rel pg_class: Uninitialized page 3353 - fixing NOTICE: Rel pg_class: Uninitialized page 3354 - fixing NOTICE: Rel pg_class: Uninitialized page 3355 - fixing NOTICE: Rel pg_class: Uninitialized page 3356 - fixing batch/nachts.sh: line 3: 30855 Segmentation fault /usr/bin/php -q /usr/local/httpd/htdocs/kunden/web41/html/wcopy/batch/vacuum.php Running VACUUM FULL ANALYZE another time there were no errors. hi, it does sound ugly. I checked the hardware. I can't see any problems with i t. I know, somestimes you need a lot of luck to see a CPU problem under solari s. But I think the hardware is ok. however, what kind of details do you need t o qualify if it's a postgres problem or not ? regards -andreas schmitz -- +++ GMX - Mail, Messaging more http://www.gmx.net +++ Bitte lächeln! Fotogalerie online mit GMX ohne eigene Homepage! ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [ADMIN] Still a bug in the VACUUM ??? !!!
Andreas Schmitz [EMAIL PROTECTED] writes: however, what kind of details do you need to qualify if it's a postgres problem or not ? Ultimately, we need a way to reproduce the problem for debugging. If it is a Postgres bug, it should be possible to reproduce it. regards, tom lane ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
Re: [ADMIN] Still a bug in the VACUUM ??? !!!
daniel alvarez [EMAIL PROTECTED] writes: NOTICE: Rel pg_class: Uninitialized page 3344 - fixing NOTICE: Rel pg_class: Uninitialized page 3345 - fixing NOTICE: Rel pg_class: Uninitialized page 3346 - fixing NOTICE: Rel pg_class: Uninitialized page 3347 - fixing NOTICE: Rel pg_class: Uninitialized page 3348 - fixing NOTICE: Rel pg_class: Uninitialized page 3349 - fixing [etc] This is a known and not very serious problem --- see http://archives.postgresql.org/pgsql-hackers/2002-11/msg00486.php batch/nachts.sh: line 3: 30855 Segmentation fault /usr/bin/php -q /usr/local/httpd/htdocs/kunden/web41/html/wcopy/batch/vacuum.php As best I can tell, that's your own client code crashing, not Postgres. regards, tom lane ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED])
[ADMIN] initdb fails after installation on Mac OS X 10.2
I've had PostgreSQL 7.1.3 running (Mac OS X) for a while. I recently upgraded to MAC OS X 10.2 (and it appeared that my 7.1.3 install of PostgreSQL no longer works). So I've been trying to upgrade to 7.3. The installation package ran fine. However, when I ran the initdb command, it failed. The only thing I did in preparation for installing 7.3 was to wipe the contents of /usr/local/pgsql/data. This is the error when I run the following command: . . . [Craig-Lawtons-Computer:/usr/local/pgsql] postgres% /usr/local/bin/initdb -D /usr/local/pgsql/data The files belonging to this database system will be owned by user postgres. This user must also own the server process. The database cluster will be initialized with locale C. Fixing permissions on existing directory /usr/local/pgsql/data... ok creating directory /usr/local/pgsql/data/base... ok creating directory /usr/local/pgsql/data/global... ok creating directory /usr/local/pgsql/data/pg_xlog... ok creating directory /usr/local/pgsql/data/pg_clog... ok creating template1 database in /usr/local/pgsql/data/base/1... dyld: /usr/local/bin/postgres Undefined symbols: /usr/local/bin/postgres undefined reference to _crypt expected to be defined in /usr/lib/libcrypto.0.9.dylib /usr/local/bin/initdb: line 582: 2642 Trace/BPT trap $PGPATH/postgres -boot -x1 $PGSQL_OPT $BACKEND_TALK_ARG template1 initdb failed. . . . Any help would be greatly appreciated. Thanks, Craig Lawton ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
