|From:||Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>|
|To:||Robert Haas <robertmhaas(at)gmail(dot)com>|
|Cc:||Jeevan Chalke <jeevan(dot)chalke(at)enterprisedb(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>|
|Subject:||Re: Server crash (FailedAssertion) due to catcache refcount mis-handling|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Tue, Aug 8, 2017 at 10:48 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>>> On Tue, Aug 8, 2017 at 4:34 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>>> In the meantime, I think my vote would be to remove AtEOXact_CatCache.
>>> In all supported branches?
>> Whatever we do about this issue, I don't feel a need to do it further
>> back than HEAD. It's a non-problem except in an assert-enabled build,
>> and we don't recommend running those for production, only development.
> Sure, but people still do testing and development against older
> branches - bug fixes, for example. It doesn't make much sense to me
> to leave code that we know does the wrong thing in the back branches.
Not having heard anyone arguing against that, I'll go make it so,
ie AtEOXact_CatCache is toast in all branches.
regards, tom lane
|Next Message||Peter Geoghegan||2017-08-13 19:19:32||Re: Thoughts on unit testing?|
|Previous Message||Fabien COELHO||2017-08-13 18:33:32||Re: pgbench - allow to store select results into variables|