Re: pg_dumpall failing from possible corrupted shared memory

Поиск
Список
Период
Сортировка
От Richard Broersma Jr
Тема Re: pg_dumpall failing from possible corrupted shared memory
Дата
Msg-id 950644.56008.qm@web31812.mail.mud.yahoo.com
обсуждение исходный текст
Ответ на Re: pg_dumpall failing from possible corrupted shared memory  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: pg_dumpall failing from possible corrupted shared memory  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-general
> No, you just need to make sure the postmaster is started under
> "ulimit -c unlimited", not "ulimit -c 0" which is the default
> under many Linuxen.  Adding this to the start script is the
> easiest way usually.
>
> If you can't get anything but numbers from gdb's stack trace
> then you have a "stripped" executable and you will need to
> rebuild to get a useful stack trace.

You'll have to forgive me. I've never used gdb before, I am not sure I am executing gdb with the
correct syntax.  However, I was able to produce a core file.  Here is the syntax that I used that
produced the most output - althought it doesn't look like what you would want.




postgres@db_server01 /home/data $ gdb postgres ./core
GNU gdb 6.4
Copyright 2005 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i686-pc-linux-gnu"...(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".


warning: core file may not match specified executable file.
(no debugging symbols found)
Core was generated by `postgres: postgres mydb [local] SELECT       '.
Program terminated with signal 11, Segmentation fault.

warning: Can't read pathname for load map: Input/output error.
Reading symbols from /lib/libpam.so.0...(no debugging symbols found)...done.
Loaded symbols for /lib/libpam.so.0
Reading symbols from /usr/lib/libssl.so.0.9.7...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libssl.so.0.9.7
Reading symbols from /usr/lib/libcrypto.so.0.9.7...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libcrypto.so.0.9.7
Reading symbols from /lib/libz.so.1...(no debugging symbols found)...done.
Loaded symbols for /lib/libz.so.1
Reading symbols from /lib/libreadline.so.5...(no debugging symbols found)...done.
Loaded symbols for /lib/libreadline.so.5
Reading symbols from /lib/libcrypt.so.1...(no debugging symbols found)...done.
Loaded symbols for /lib/libcrypt.so.1
Reading symbols from /lib/libresolv.so.2...(no debugging symbols found)...done.
Loaded symbols for /lib/libresolv.so.2
Reading symbols from /lib/libnsl.so.1...(no debugging symbols found)...done.
Loaded symbols for /lib/libnsl.so.1
Reading symbols from /lib/libdl.so.2...(no debugging symbols found)...done.
Loaded symbols for /lib/libdl.so.2
Reading symbols from /lib/libm.so.6...(no debugging symbols found)...done.
Loaded symbols for /lib/libm.so.6
Reading symbols from /lib/libc.so.6...(no debugging symbols found)...done.
Loaded symbols for /lib/libc.so.6
Reading symbols from /lib/libncurses.so.5...(no debugging symbols found)...done.
Loaded symbols for /lib/libncurses.so.5
Reading symbols from /lib/ld-linux.so.2...(no debugging symbols found)...done.
Loaded symbols for /lib/ld-linux.so.2
Reading symbols from /lib/libnss_compat.so.2...(no debugging symbols found)...done.
Loaded symbols for /lib/libnss_compat.so.2
Reading symbols from /lib/libnss_nis.so.2...(no debugging symbols found)...done.
Loaded symbols for /lib/libnss_nis.so.2
Reading symbols from /lib/libnss_files.so.2...(no debugging symbols found)...done.
Loaded symbols for /lib/libnss_files.so.2
#0  0xb7cc871b in strtouq () from /lib/libc.so.6
gdb> stack
#0  0xb7cc871b in strtouq () from /lib/libc.so.6
#1  0xb7cc847f in __strtol_internal () from /lib/libc.so.6
#2  0x08178404 in nodeToString ()
#3  0x081794fa in parseNodeString ()
#4  0x0817b2ff in nodeRead ()
#5  0x0817b16f in nodeRead ()
#6  0x081780ed in nodeToString ()
#7  0x081795fa in parseNodeString ()
#8  0x0817b2ff in nodeRead ()
#9  0x0817b16f in nodeRead ()
#10 0x0817b839 in stringToNode ()
#11 0x082264fb in pg_get_constraintdef ()
#12 0x0822667e in pg_get_indexdef ()
#13 0x08144ff5 in ExecProject ()
#14 0x081449ef in ExecProject ()
#15 0x08153aa5 in ExecMergeJoin ()
#16 0x081441bf in ExecProcNode ()
#17 0x081552f5 in ExecSort ()
#18 0x081441ed in ExecProcNode ()
#19 0x08143574 in ExecutorRun ()
#20 0x081dcbd9 in PostgresMain ()
#21 0x081dd1d8 in PortalRun ()
#22 0x081d8fab in pg_parse_and_rewrite ()
#23 0x081db364 in PostgresMain ()
#24 0x081a7db4 in ClosePostmasterPorts ()
#25 0x081a8ecc in PostmasterMain ()
#26 0x08165629 in main ()
gdb>


Please let me know what I can do to produce output that is more inline with what you expect.

Thanks for the help.

Regards,

Richard Broersma Jr.

В списке pgsql-general по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: Possible problem with PQescapeStringConn and standard_conforming_strings
Следующее
От: Tom Lane
Дата:
Сообщение: Re: pg_dumpall failing from possible corrupted shared memory