RE: [HACKERS] How do I get the backend server into gdb?

From: Michael J Davis <michael(dot)j(dot)davis(at)tvguide(dot)com>
To: "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, hackers(at)postgreSQL(dot)org
Subject: RE: [HACKERS] How do I get the backend server into gdb?
Date: 1999-04-29 23:06:49
Message-ID: 93C04F1F5173D211A27900105AA8FCFC14544E@lambic.prevuenet.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

How does this work when using Access97 or some other ODBC client instead of
psql? Psql worked great, the problem existed only when trying to access my
database with an ODBC client.

-----Original Message-----
From: Tom Lane [SMTP:tgl(at)sss(dot)pgh(dot)pa(dot)us]
Sent: Thursday, April 29, 1999 4:34 PM
To: Massimo Dal Zotto
Cc: hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] How do I get the backend server into
gdb?

Massimo Dal Zotto <dz(at)cs(dot)unitn(dot)it> writes:
> The -W option is passed to the backend which sleeps 15 seconds
before doing
> any work. In the meantime you have the time to do a ps, find the
backend pid
> and attach gdb to the process.
> Obviously you can't do that in a production environment because it
adda a
> fixed delay for each connection which will make your users very
angry.

Since it's a -o option, I see no need to force it to be used on
every
connection. Instead start psql with environment variable
PGOPTIONS="-W 15"
or whatever you need for the particular session. The PGOPTIONS are
sent
in the connection request and then catenated to whatever the
postmaster
might have in its -o switch.

(BTW, it might be a good idea to go through the backend command-line
switches carefully and see if any of them could be security holes.
I'm feeling paranoid because of Matthias Schmitt's unresolved
report...)

regards, tom lane

Browse pgsql-hackers by date

  From Date Subject
Next Message Andy Lewis 1999-04-29 23:23:35 Re: [HACKERS] PLpgSQL Stat Problem
Previous Message Tom Lane 1999-04-29 22:39:28 Re: [HACKERS] PLpgSQL Stat Problem