Re: ENOSPC FailedAssertion("!(RefCountErrors == 0)"
От | Robert Haas |
---|---|
Тема | Re: ENOSPC FailedAssertion("!(RefCountErrors == 0)" |
Дата | |
Msg-id | CA+TgmobXLXNeyod0wrmFp1xeusJJtTCzZPizqwHsfr=hVKS2DA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: ENOSPC FailedAssertion("!(RefCountErrors == 0)" (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: ENOSPC FailedAssertion("!(RefCountErrors == 0)"
|
Список | 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 по дате отправления: