| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Erik Rijkers" <er(at)xs4all(dot)nl> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: TRAP: BadArgument - mcxt.c, Line: 813 |
| Date: | 2015-03-29 17:35:19 |
| Message-ID: | 13811.1427650519@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Erik Rijkers" <er(at)xs4all(dot)nl> writes:
> I get a crash while restoring a trgm GIN index.
Hm, interesting: this seems to be the first negative fallout from
commit eaa5808e8ec4e82ce1a87103a6b6f687666e4e4c, which made
MemoryContextReset() delete not reset child contexts. ginbuild()
is creating a funcCtx as a child of its tmpCtx but then supposing
that it can reset the tmpCtx without damaging the other one.
Easy enough to fix, but it's a bit worrisome that we did not find
this in regression testing. Apparently the regression tests do
not exercise the "early dump" code path in ginBuildCallback...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fabien COELHO | 2015-03-29 17:49:30 | Re: getting rid of "thread fork emulation" in pgbench? |
| Previous Message | Pavel Stehule | 2015-03-29 17:34:40 | Re: Providing catalog view to pg_hba.conf file - Patch submission |