Re: youtube video on pgsql integrity

Поиск
Список
Период
Сортировка
От Gavan Schneider
Тема Re: youtube video on pgsql integrity
Дата
Msg-id 7929-1354253655-964692@sneakemail.com
обсуждение исходный текст
Ответ на Re: youtube video on pgsql integrity  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-general
Tom, thanks for the reply

On Thursday, November 29, 2012 at 12:58, Tom Lane wrote:

>Gavan Schneider writes:
>>pendari=> select now()/0;
>>Bus error: 10
>
>[ scratches head... ]  I get the expected error report on my own OS X
>10.7.5 machine (though it's just plain Lion not Server).
>
As of Lion the Server functionality is a simple add-on to the
base system. Seems the underlying stuff is always there just you
get the management tools and extra bell'n'whistles to configure.

>This looks like it's a psql-side problem, not a server-side problem,
>particularly since you say nothing showed up in the server log.
>
Agree that psql had a problem since it left crash logs for both
of the instances I had running in separate shells. Impressive!
almost quantum (aka spooky action at a distance) effect. Execute
stupid statement in one shell and kill your own and the other
process as well. I have found an instance of my server process
still hanging on but it is not accepting connections from psql
or pgadmin3, and at almost zero CPU time, is likely detritus
from a failed startup test.

So the psql "problem" also took the server down... to me this
all seems to point to a common piece of code with poor
interprocess separation so the misaligned libraries idea seems
to have merit.

 From the psql crash log:

     Process:         psql [94318]
     Path:            /Volumes/VOLUME/*/psql
     Identifier:      psql
     Version:         ??? (???)
     Code Type:       X86-64 (Native)
     Parent Process:  bash [69168]

     Date/Time:       2012-11-30 09:48:53.886 +1100
     OS Version:      Mac OS X Server 10.7.5 (11G63)
     Report Version:  9

     Crashed Thread:  0  Dispatch queue: com.apple.main-thread

     Exception Type:  EXC_BAD_ACCESS (SIGBUS)
     Exception Codes: 0x000000000000000a, 0x0000000100938622

     VM Regions Near 0x100938622:
         --> mapped file 0000000100930000-000000010098c000 [
368K] r-x/rwx SM=COW
                 Object_id=270c5ca0
             VM_ALLOCATE 000000010098c000-0000000100993000 [
28K] rw-/rwx SM=PRV

     Application Specific Information:
     objc[94318]: garbage collection is OFF

     Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
     0   ???                             0x0000000100938622 0 + 4304635426
     1   ???                             0x0000000100939807 0 + 4304640007
     2   ???                             0x0000000100940df6 0 + 4304670198
     3   ???                             0x0000000100931124 0 + 4304605476

     Thread 0 crashed with X86 Thread State (64-bit): ...
     Logical CPU: 0

     Binary Images:
        ... +psql (??? - ???) /Volumes/VOLUME/*/psql
        ... libssl.0.9.8.dylib (44.0.0 - compatibility 0.9.8)
.... /usr/lib/libssl.0.9.8.dylib
*==>   ... libedit.3.dylib (3.0.0 - compatibility 2.0.0) ... /usr/lib/libedit.3.dylib
        ...

 From this can I conclude:

     --  the Apple "buggy" version is the one in use?

     --  specifically, that my postgres build would not normally have
         installed this library in this location? and,

     --  do you have the GNU readline installed on your system?

(While I am having so many adventures doing the "normal" thing,
I hope you can understand why I don't want to be a pioneer as
well. :)

Regards
Gavan Schneider



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

Предыдущее
От: "Greg Sabino Mullane"
Дата:
Сообщение: Re: pg_listening_channels()
Следующее
От: Justin Julicher
Дата:
Сообщение: Updating pg_attribute to widen column