Tom Lane wrote:
> Define "die quite nastily" ... you haven't really said what went wrong.
>
We lost data from this table, and ended up with transactions rolled back
that were in fact committed (ie. data was in DB, program code thought
they were rolled back).
End result was we deemed the databas
Philip Warner <[EMAIL PROTECTED]> writes:
> We just had a DB die quite nastily, and have no clear idea why.
Define "die quite nastily" ... you haven't really said what went wrong.
> 2006-01-25 12:25:31 EST [mail,5017]: ERROR: failed to fetch new tuple
> for AFTER trigger
> 2006-01-25 12:26:01 ES
Philip Warner wrote:
> We just had a DB die quite nastily, and have no clear idea why.
>
> Looking in the system logs shows nothing out of the ordinary, and
> looking in the db logs shows a few odd records:
>
> 2006-01-25 12:25:31 EST [mail,5017]: ERROR: failed to fetch new tuple
> for AFTER tri
We just had a DB die quite nastily, and have no clear idea why.
Looking in the system logs shows nothing out of the ordinary, and
looking in the db logs shows a few odd records:
2006-01-25 12:25:31 EST [mail,5017]: ERROR: failed to fetch new tuple
for AFTER trigger
2006-01-25 12:26:01 EST [mail,
