Seems to be working fine now that I've upgraded to 12.1. I'll keep an eye
out for 12.2. However, we are not using a before row update trigger. We are
using an after insert trigger on the containers table though.
Thanks,
Doug
On Tue, Feb 4, 2020 at 2:34 PM Tom Lane wrote:
>
ine 216 C
[External Code]
On Tue, Feb 4, 2020 at 11:40 AM Adrian Klaver
wrote:
> On 2/4/20 6:20 AM, Doug Roberts wrote:
> >> So how did containers_reset_recirc() come to clash with
> >> containers_add_update()?
> >
> > They are clashing because another
Sure. Ok then.
On Tue, Feb 4, 2020 at 11:18 AM Adrian Klaver
wrote:
> On 2/4/20 8:06 AM, Doug Roberts wrote:
> > Hello,
> >
> > Here is a stacktrace of what happened before and after the crash.
>
> Actually the below is the Postgres log. Per Tom's previous pos
LOCATION: StartupXLOG, xlog.c:7307
2020-02-04 10:26:55.861 EST [16700] [0] FATAL: 57P03: the database system
is in recovery mode
2020-02-04 10:26:55.861 EST [16700] [0] LOCATION: ProcessStartupPacket,
postmaster.c:2275
2020-02-04 10:26:57.016 EST [20788] [0] LOG: 0: database system is
rea
PM Tom Lane wrote:
> Adrian Klaver writes:
> > Please reply to list also.
>
> > On 2/3/20 2:18 PM, Doug Roberts wrote:
> >> Here is what the reset recirc function is doing.
> >> ...
> >> UPDATE containers
> >> ...
>
> > So how did c
Hello,
I'm having an issue where a process in Postgres is crashing and cause the
server to go into recovery mode.
I'm getting the following errors in the log.
2020-02-03 14:12:57.473 EST [11992] [0]WARNING: 57P02: terminating
connection because of crash of another server process
2020-02-03 14:1
