| From: | Mark Kirkwood <markir(at)paradise(dot)net(dot)nz> |
|---|---|
| To: | Nailah Ogeer <ogeer(at)cs(dot)queensu(dot)ca> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Elog |
| Date: | 2003-05-30 23:02:03 |
| Message-ID: | 3ED7E2EB.3060003@paradise.net.nz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
Nailah Ogeer wrote:
>Where do the elog information go in postgres7.3.2.
>
To whereever you have told the server to log (stdout if you havent
specified)
> I am still getting a
>Segmentation fault when trying to run my code after making changes to the
>buffer folder and relcache.c. Someone mentioned using a stack before to
>trace. Can someone give me some more info on this or other methods of
>tracing?
>
>
Use something like strace (Linux) or truss (Solaris) and attach it to
your backend process.
If your crash happens immediately, then run a single process backend and
trace it from startup.
regards
Mark
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-05-30 23:17:32 | Re: Moving a table to a different schema |
| Previous Message | Robert Treat | 2003-05-30 22:03:32 | Re: Re-Create Table make Faster. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Brusser | 2003-05-30 23:03:45 | Re: Practical sets of SQLSTATE values? |
| Previous Message | Sean Chittenden | 2003-05-30 20:20:28 | Re: XML ouput for psql |