>From the logs tonight when the second crash occurred..
Aug 22 20:45:12 db-1 postgres[5805]: [ID 748848
local0.info] [6-1] 2007-08-22 20:45:12 CDT LOG:
received smart shutdown request
Aug 22 20:45:12 db-1 postgres[5805]: [ID 748848
local0.info] [7-1] 2007-08-22 20:45:12 CDT LOG:
server process (PID 20188) was terminated by signal 11
Aug 22 20:45:12 db-1 postgres[5805]: [ID 748848
local0.info] [8-1] 2007-08-22 20:45:12 CDT LOG:
terminating any other active server processes
There was a core file created...but I believe I do not
have postgresql compiled with debug info.....(well, a
pstack provided nothing useful)
pstack core |more
core 'core' of 20188: /usr/local/pgsql/bin/postgres
-D /db
fee8ec23 sk_value (10023d, 105d8b00, d2840f,
1c7f0000, f20f883, 10584) + 33
0c458b51 ???????? (0, 0, 511f1600, 2000400, ff001c09,
467f71ea)
00000000 ???????? ()
Once again...a local pg_dump worked just fine 30
minutes later......
We have introduced some new network architecture which
is acting odd lately (dell managed switches, netscreen
ssgs, etc) and the database itself resides on a zfs
partition on a Pillar SAN (connected via fibre
channel)
Any thoughts would be appreciated.
____________________________________________________________________________________
Pinpoint customers who are looking for what you sell.
http://searchmarketing.yahoo.com/
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
