Re: "invalid memory alloc request size <n>" in deferred trigger causes transaction to fail, but the backend keeps running

> > #1 0x0818e9e1 in SendPostmasterSignal (reason=PMSIGNAL_PASSWORD_CHANGE)
> > at pmsignal.c:69
> >
> > As far as the other problem is concerned, I just finished the first half
> > of the conversion on a different machine that was build with assertions
> > enabled and saw a number of reports like the ones below. What's causing
> > these?
>
> This happens when a transaction finishes that creates, drops, or
> modifies a user. If it happens at a different time, something is wrong.

The code for the first part of the conversion does not contain any statements
for create/alter/drop user, it doesn't even fire triggers. Basically it's
just looping over the following set of statements for a number of textfiles:

- read, validate and post-process the contents of a text file
- write the result into another text file
- (try to) drop the table
- create the table
- grant select on this table to public
- copy table from a textfile

That's it, so there is no explicit user-handling at all.

Anything particular I can take a look at?

--
Best,

Frank.