I'd love to send you a stack trace. Any suggestions on how to get one? It has since happened again, on the same update command, so I'm guessing I can repeat it.
On Thu, Dec 30, 2010 at 6:52 PM, Tom Lane-2 [via PostgreSQL] < ml-node+3323151-436577542-56...@n5.nabble.com<ml-node%2b3323151-436577542-56...@n5.nabble.com> > wrote: > Gordon Shannon <[hidden > email]<http://user/SendEmail.jtp?type=node&node=3323151&i=0>> > writes: > > Running Centos, just upgraded our production db from 8.4.4 to 9.0.2 last > > night. About 20 hours later, an update statement seg faulted and crashed > > > the server. This is a typical update that has worked fine for a long > time. > > Could we see a stack trace from that? Or at least a self-contained > test case? > > regards, tom lane > > -- > Sent via pgsql-general mailing list ([hidden > email]<http://user/SendEmail.jtp?type=node&node=3323151&i=1>) > > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-general > > > ------------------------------ > View message @ > http://postgresql.1045698.n5.nabble.com/seg-fault-crashed-the-postmaster-tp3323117p3323151.html > To unsubscribe from seg fault crashed the postmaster, click > here<http://postgresql.1045698.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=3323117&code=Z29yZG8xNjlAZ21haWwuY29tfDMzMjMxMTd8LTEwNjcwMjEwNDQ=>. > > -- View this message in context: http://postgresql.1045698.n5.nabble.com/seg-fault-crashed-the-postmaster-tp3323117p3323171.html Sent from the PostgreSQL - general mailing list archive at Nabble.com.
