Re: Notify system doesn't recover from "No space" error

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Notify system doesn't recover from "No space" error
Date: 2012-02-09 18:43:37
Message-ID: 4F33BF790200002500045121@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> wrote:

> In continued digging through logs I found something to indicate
> the transaction on which COMMIT failed for 2528 of the failures.
> In all cases the transaction made a change which would have fired
> a NOTIFY at commit (in a deferred trigger).

Arg. Sorry, I got confused there. No deferred trigger involved in
the triggered change notification; that is only in the replication
code. I haven't seen anything to suggest that the replication
trigger is contributing to this, but I guess I couldn't rule it out,
either.

-Kevin

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2012-02-09 19:38:27 Re: When do we lose column names?
Previous Message Kevin Grittner 2012-02-09 18:37:25 Re: Notify system doesn't recover from "No space" error