On Aug 17 10:38, Tom Lane wrote:
Volkan YAZICI [EMAIL PROTECTED] writes:
I've still biten by a single write past chunk error while returning a
record in PL/scheme:
WARNING: problem in alloc set ExprContext: detected write past chunk
end in block 0x84a0598, chunk 0x84a0c84
The
Volkan YAZICI [EMAIL PROTECTED] writes:
Looks like my palloc() math was correct. Just I had missed special
handling of attnulls array passed to heap_formtuple(). It had should be
attnulls[i] = (isnull) ? 'n' : ' ';
These days I'd use heap_form_tuple in new code --- then you can work
with
On Aug 16 04:20, Volkan YAZICI wrote:
On Aug 16 03:09, Volkan YAZICI wrote:
WARNING: problem in alloc set ExprContext: detected write past chunk
end in block 0x8462f00, chunk 0x84634c8
WARNING: cache reference leak: cache pg_type (34), tuple 2/7 has
count 1
Excuse me for bugging the
Hi,
I've been trying to implement INOUT/OUT functionality in PL/scheme. When
I return a record type tuple, postmaster complains with below warnings:
WARNING: problem in alloc set ExprContext: detected write past chunk
end in block 0x8462f00, chunk 0x84634c8
WARNING: cache reference leak: cache
On Aug 16 03:09, Volkan YAZICI wrote:
WARNING: problem in alloc set ExprContext: detected write past chunk
end in block 0x8462f00, chunk 0x84634c8
WARNING: cache reference leak: cache pg_type (34), tuple 2/7 has
count 1
Excuse me for bugging the list. I've solved the problem. I should look