pgsql/src/backend/libpq (be-fsstubs.c be-pqexec.c pqsignal.c)

Started by Tom Lane <>almost 26 years ago3 messagescomitters
Jump to latest
#1Tom Lane <>
tom_lane___@unknown.user

Date: Tuesday, June 27, 2000 @ 23:31:42
Author: tgl

Update of /home/projects/pgsql/cvsroot/pgsql/src/backend/libpq
from hub.org:/home/projects/pgsql/tmp/cvs-serv57303/src/backend/libpq

Modified Files:
be-fsstubs.c be-pqexec.c pqsignal.c

----------------------------- Log Message -----------------------------

First phase of memory management rewrite (see backend/utils/mmgr/README
for details). It doesn't really do that much yet, since there are no
short-term memory contexts in the executor, but the infrastructure is
in place and long-term contexts are handled reasonably. A few long-
standing bugs have been fixed, such as 'VACUUM; anything' in a single
query string crashing. Also, out-of-memory is now considered a
recoverable ERROR, not FATAL.
Eliminate a large amount of crufty, now-dead code in and around
memory management.
Fix problem with holding off SIGTRAP, SIGSEGV, etc in postmaster and
backend startup.

#2Hiroshi Inoue
Inoue@tpf.co.jp
In reply to: Tom Lane <> (#1)
Re: pgsql/src/backend/libpq (be-fsstubs.c be-pqexec.c pqsignal.c)

Tom Lane wrote:

Date: Tuesday, June 27, 2000 @ 23:31:42
Author: tgl

Update of /home/projects/pgsql/cvsroot/pgsql/src/backend/libpq
from hub.org:/home/projects/pgsql/tmp/cvs-serv57303/src/backend/libpq

Modified Files:
be-fsstubs.c be-pqexec.c pqsignal.c

----------------------------- Log Message -----------------------------

First phase of memory management rewrite (see backend/utils/mmgr/README
for details). It doesn't really do that much yet, since there are no
short-term memory contexts in the executor, but the infrastructure is
in place and long-term contexts are handled reasonably. A few long-
standing bugs have been fixed, such as 'VACUUM; anything' in a single
query string crashing. Also, out-of-memory is now considered a
recoverable ERROR, not FATAL.
Eliminate a large amount of crufty, now-dead code in and around
memory management.
Fix problem with holding off SIGTRAP, SIGSEGV, etc in postmaster and
backend startup.

I got a compile error in pqsignal.c.
Seems Linux doesn't have SIGSYS.

kill -l
1) SIGHUP 2) SIGINT 3) SIGQUIT 4) SIGILL
5) SIGTRAP 6) SIGABRT 7) SIGBUS 8) SIGFPE
9) SIGKILL 10) SIGUSR1 11) SIGSEGV 12) SIGUSR2
13) SIGPIPE 14) SIGALRM 15) SIGTERM 17) SIGCHLD
18) SIGCONT 19) SIGSTOP 20) SIGTSTP 21) SIGTTIN
22) SIGTTOU 23) SIGURG 24) SIGXCPU 25) SIGXFSZ
26) SIGVTALRM 27) SIGPROF 28) SIGWINCH 29) SIGIO
30) SIGPWR

Regards.

Hiroshi Inoue

#3Tom Lane
tgl@sss.pgh.pa.us
In reply to: Hiroshi Inoue (#2)
Re: pgsql/src/backend/libpq (be-fsstubs.c be-pqexec.c pqsignal.c)

Hiroshi Inoue <Inoue@tpf.co.jp> writes:

Fix problem with holding off SIGTRAP, SIGSEGV, etc in postmaster and
backend startup.

I got a compile error in pqsignal.c.
Seems Linux doesn't have SIGSYS.

OK, I'll clean it up later today, but if you're in a hurry just put an
#ifdef SIGSYS around the line that tries to turn off SIGSYS trapping.

regards, tom lane