[BUGS]
I can not access a table if it is uppercase without putting quotes around it..
[BUGS] Error while doing a Vacuum
Hello, I have a problem when I ran a VACUUM on a Postgresql database, I had tried to do it a few times and the vacuum always stop in the same place with the same error (or message), and it takes more than one hour before I got it. The message that I get is in spanish and it says : No space left on the device. PostgreSQL version: 7.1.2 System: RedHat Linux 7.0 Computer PIII 800 Mhz 256 Mg RAM 665 NOTICE: --Relation gdinformesm-- 666 NOTICE: Pages 40221: Changed 0, reaped 26022, Empty 0, New 0; Tup 893413: Vac 896414, Keep/VTL 0/0, Crash 0, UnUsed 85438, MinLen 109, MaxLen 201; Re-using: Free/Avail. Space 172320356/172312672; EndEmpty/Avail. Pages 0/26021. CPU 2.13s/0.68u sec. 667 NOTICE: Index i2informesm: Pages 17316; Tuples 893413: Deleted 520320. CPU 2.94s/8.27u sec. 668 NOTICE: Index i3informesm: Pages 27041; Tuples 893413: Deleted 520320. CPU 2.70s/7.02u sec. 669 NOTICE: Index i4informesm: Pages 10214; Tuples 893413: Deleted 520320. CPU 1.40s/7.29u sec. 670 NOTICE: Index i5informesm: Pages 4739; Tuples 893413: Deleted 520319. CPU 1.21s/8.40u sec. 671 NOTICE: Index i6informesm: Pages 9873; Tuples 893413: Deleted 520319. CPU 1.26s/7.10u sec. 672 NOTICE: Index i7informesm: Pages 14643; Tuples 893413: Deleted 520319. CPU 1.59s/6.44u sec. 673 NOTICE: Index i8informesm: Pages 12466; Tuples 893413: Deleted 520319. CPU 1.41s/7.08u sec. 674 NOTICE: Index gdinformesm_codiinfo_key: Pages 5133; Tuples 893413: Deleted 520319. CPU 1.10s/6.94u sec. 675 NOTICE: Index i9informesm: Pages 9690; Tuples 893413: Deleted 520319. CPU 1.54s/7.01u sec. 676 NOTICE: Index i10informes: Pages 5934; Tuples 893413: Deleted 520319. CPU 1.28s/6.90u sec. 677 FATAL 2: ZeroFill(/data/pgsql/pg_xlog/xlogtemp.15100) failed: No queda espacio en el dispositivo 678 pqReadData() -- backend closed the channel unexpectedly. 679 This probably means the backend terminated abnormally 680 before or while processing the request. 681 connection to server was lost Regards, Miguel Juan Mallorca (Spain) ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
[BUGS] Mac OS X 10.1 build bug - paths with spaces
Operating System: Mac OS X 10.1.1 (Build 5M28) PostgreSQL Version: CVS checkout as of Nov 17, 2001 Problem Category: Building After running ./configure and then "make all" the build stopped with the message cc -traditional-cpp -g -O2 -Wall -Wmissing-prototypes -Wmissing-declarations -I../../../src/include -c -o analyze.o analyze.c analyze.c:23: parser/parse.h: No such file or directory I looked at the part of the build messages where parse.h is supposed to get built and I didn't see any problems: make -C parser parse.h bison -y -d gram.y mv -f y.tab.c ./gram.c mv -f y.tab.h ./parse.h prereqdir=`cd parser/ >/dev/null && pwd` && \ cd ../../src/include/parser/ && rm -f parse.h && \ ln -s $prereqdir/parse.h . with no error messages. The base directory of my build was /Volumes/SCSI Volume/devel/pgsql. I had a wild hunch that the space in the "SCSI Volume" part of my path was to blame, so I unpacked a clean copy of the source material to /usr/local/src/pgsql (no spaces in path name), redid the ./configure and make phase and all built fine. Obviously this is hampering my development, but I figured I'd pass it along since you never know who's going to get hit unawares with this. (Especially those pesky Mac people who like spaces in their folder names.) Cheers! Murray Todd Williams ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [BUGS] Mac OS X 10.1 build bug - paths with spaces
Murray Todd Williams <[EMAIL PROTECTED]> writes: > The base directory of my build was /Volumes/SCSI Volume/devel/pgsql. I > had a wild hunch that the space in the "SCSI Volume" part of my path was > to blame, so I unpacked a clean copy of the source material to > /usr/local/src/pgsql (no spaces in path name), redid the ./configure and > make phase and all built fine. Looks like we need some double quotes in that there ln -s command. I'll try this here to see if there are any other places with the same problem. 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])
Re: [BUGS] Mac OS X 10.1 build bug - paths with spaces
I said: > Looks like we need some double quotes in that there ln -s command. Sure enough, you can build in a directory whose path contains spaces after addition of double quotes to src/backend/Makefile's ln -s command for parse.h. However, I found that a lot of things blow up if you try to specify an installation prefix that contains spaces in the pathname. configure itself failed to cope with "--prefix=/path/with/spaces", for reasons that aren't very clear to me. I gave up when I found that initdb couldn't deal with spaces in $PATH. There might be other problems further downstream. Cleaning this up might be a project for some future hacker, but I haven't got time for it now... regards, tom lane ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [BUGS]
> I can not access a table if it is uppercase without putting quotes around it.. Yes, this is known behavior, per SQL standard. -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup.| Drexel Hill, Pennsylvania 19026 ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
