From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Lee Kindness <lkindness(at)csl(dot)co(dot)uk> |
Cc: | "Amit Khare" <khare(at)uiuc(dot)edu>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: How to Run postgres inside gdb for debugging |
Date: | 2002-02-23 19:01:11 |
Message-ID: | 25647.1014490871@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Lee Kindness <lkindness(at)csl(dot)co(dot)uk> writes:
> The problem is you'll need to do this very fast - this is why postgres
> has a '-W' option to tell the process to wait a defined time before
> really starting up - giving you time to connect. See:
> http://www.geocrawler.com/archives/3/10/1999/4/0/1649841/
It's not necessary to use -W unless you are trying to debug something
that happens during the backend startup process. Even then, I wouldn't
make it a postmaster parameter, because that causes *all* started
backends to delay. Instead say export PGOPTIONS="-W n" on the client
side before you start psql, so the delay only applies to your backend
under test. See
http://archives.postgresql.org/pgsql-hackers/2000-01/msg01463.php
(Bruce said he was going to put that info into FAQ_DEV, but he never
did...)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-02-23 19:03:13 | Re: Wierdness using SUM to add results of custom C function. |
Previous Message | Doug McNaught | 2002-02-23 18:43:33 | Re: permissions |