Re: ENOSPC FailedAssertion("!(RefCountErrors == 0)" - Mailing list pgsql-hackers

From Robert Haas
Subject Re: ENOSPC FailedAssertion("!(RefCountErrors == 0)"
Date
Msg-id CA+TgmobXLXNeyod0wrmFp1xeusJJtTCzZPizqwHsfr=hVKS2DA@mail.gmail.com
Whole thread Raw
In response to Re: ENOSPC FailedAssertion("!(RefCountErrors == 0)"  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: ENOSPC FailedAssertion("!(RefCountErrors == 0)"  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Wed, Jul 18, 2018 at 10:33 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> So couldn't we use TopTransactionResourceOwner instead of
>> AuxProcessResrouceOwner? I feel a bit uneasy that bootstrap and
>> standalone-backend have *AuxProcess*ResourceOwner.
>
> Since the aux processes aren't running transactions, I didn't think
> that TopTransactionResourceOwner was appropriate.  There's also
> a problem for bootstrap and standalone backend cases: those do run
> transactions and therefore create/destroy TopTransactionResourceOwner,
> leaving nothing behind for ShutdownXLOG to use if it tries to use
> that.  We need an extra resowner somewhere.

FallbackResourceOwner?  DefaultResourceOwner? SessionResourceOwner?

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [HACKERS] logical decoding of two-phase transactions
Next
From: Marco van Eck
Date:
Subject: Have an encrypted pgpass file