From: | "Roberts, Jon" <Jon(dot)Roberts(at)asurion(dot)com> |
---|---|
To: | "Magnus Hagander" <magnus(at)hagander(dot)net> |
Cc: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: pg crashing |
Date: | 2008-07-02 14:36:44 |
Message-ID: | 1A6E6D554222284AB25ABE3229A92762E9A696@nrtexcus702.int.asurion.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
>
> Not having looked at the internals of db_link, I'd say it's certainly
> possible that this is the reason for the failed restart. If db_link is
> blocking something, the postmaster can't kill it off, and it'll still
be
> sitting there holding a reference to the shared memory segment.
>
> That said, it shouldn't be the reason why it's crashing in the first
> place - just the reason why it won't restart properly.
>
Is this a problem in Unix? We are about 1 - 2 weeks away from moving
this database to Solaris.
Jon
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2008-07-02 14:39:26 | Re: SRF written in C |
Previous Message | Craig Ringer | 2008-07-02 14:35:29 | Re: Postgres benchmark? |
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2008-07-02 14:43:11 | Re: pg crashing |
Previous Message | Tom Lane | 2008-07-02 14:28:01 | Re: Location for pgstat.stat |