Re: invalid memory alloc request size error with commit 4b93f579

Rushabh Lathia <rushabh.lathia@gmail.com>

From: Rushabh Lathia <rushabh.lathia@gmail.com>

To: Tom Lane <tgl@sss.pgh.pa.us>

Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>

Date: 2018-02-27T01:57:45Z

Lists: pgsql-hackers

Thanks Tom.

On Tue, Feb 27, 2018 at 2:55 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:

> I wrote:
> > I wonder whether it is worth creating a C trigger function
> > (probably in regress.c) specifically to exercise this situation.
>
> Actually, that doesn't seem too bad at all.  I propose applying
> and back-patching the attached.
>
>
Patch looks good to me.


> BTW, I noticed while doing this that the adjacent "funny_dup17"
> trigger is dead code, and has been since commit 1547ee01 of
> 1999-09-29.  I'm inclined to rip it out, because anyone looking
> at regress.c would naturally assume that anything in there is
> being exercised.
>
>                         regards, tom lane
>
>


-- 
Rushabh Lathia

Commits

Prevent dangling-pointer access when update trigger returns old tuple.
- 25b692568f42 11.0 landed
- b45f821e2226 10.4 landed
- 9bc33ef5ece9 9.3.23 landed
- 5ccb77586955 9.4.18 landed
- 2ee44e10d44b 9.5.13 landed
- 06f47297e2b0 9.6.9 landed
Improve regression test coverage of regress.c.
- be42eb9d624c 11.0 landed
Remove unused functions in regress.c.
- db3af9feb19f 11.0 landed
Make plpgsql use its DTYPE_REC code paths for composite-type variables.
- 4b93f57999a2 11.0 cited
This is part #1 for of the DEFERRED CONSTRAINT TRIGGER support.
- 1547ee017c89 7.1.1 cited