If you do decide to prefix DEBUG, please consider prefixing at least ERROR
as well. It produces a lot of warnings when compiling on Win32 (ERROR is
already defined as part of the standard windows headers). It's just
warnings, though.
//Magnus
> Do other people have a comment on this. I am incl
Sorry for the delay but I can't find gdb.
I already looked at the doc/FAQ_QNX4 file but I didn't find any help.
At the moment I'm tring to fix the problem, also with the QNX italian
reseller, but we can't undestand if the problem is the QNX configuration or
the PGSQL QNX version.
Today I also t
Hi,
There seems to be a problem in the configure script for solaris.
(Recent CVS copy)
./configure
checking for POSIX signal interface... (cached) yes
./configure: syntax error at line 6907: `;' unexpected
A "for" construct, traced back to config/tcl.m4, is upsetting
the shell interpr
Keith Parks writes:
> for pgac_dir; do
> if test -r "$pgac_dir/tclConfig.sh"; then
> TCL_CONFIG_SH=$pgac_dir/tclConfig.sh
> break
> fi
> done
>
> fails
Thanks. The semicolon is actually only needed (allowed) with an `in'
clause.
--
Peter Eisen
I have a table. When I vacuum verbose it...
mail=# vacuum verbose tblemaildomain ;
NOTICE: --Relation tblemaildomain--
NOTICE: Pages 199: Changed 0, reaped 0, Empty 0, New 0; Tup 27494: Vac 0,
Keep/VTL 1/0, Crash 0, UnUsed 0, MinLen 40, MaxLen 80; Re-using:
Free/Avail. Space 0/0; EndEmpty/Avai
