| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Kevin Grittner" <kgrittn(at)mail(dot)com> |
| Cc: | "Stefan Kaltenbrunner" <stefan(at)kaltenbrunner(dot)cc>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: strange isolation test buildfarm failure on guaibasaurus |
| Date: | 2012-12-06 04:47:20 |
| Message-ID: | 23050.1354769240@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Kevin Grittner" <kgrittn(at)mail(dot)com> writes:
> Stefan Kaltenbrunner wrote:
>> seems like a rather odd failure in the isolation test (client)
> Lines which might get the attention of interested parties:
> TRAP: FailedAssertion("!(rel->rd_refcnt > 0)", File: "relcache.c", Line: 1603)
Hah ... I'd looked at that report but managed to miss the TRAP entry.
It's yet another silliness in the DROP INDEX CONCURRENTLY patch,
which I'm now kicking myself for not noticing when I reviewed the
patch last week:
http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=e31d524867130d3c54b8d5f4c5ed59e2fcd07867
We really need to scare up another buildfarm member to run with
-DCLOBBER_CACHE_ALWAYS, now that jaguar has stopped doing so.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Shigeru Hanada | 2012-12-06 04:47:22 | Re: PATCH: optimized DROP of multiple tables within a transaction |
| Previous Message | Amit Kapila | 2012-12-06 04:42:31 | Re: Proposal for Allow postgresql.conf values to be changed via SQL |