Stefan Niantschur <sniantschur@xxxxxx> writes: > Am Sun, 17 Feb 2008 09:17:08 -0500 > schrieb Tom Lane <tgl@xxxxxxxxxxxxx>: >> Hardly surprising when you're printing the string into a fixed-size >> 8K buffer. The buffer overflow is smashing the stack, in particular >> the function's return address. > Yes, I know, but the backend does not allow for a bigger buffer. Trying > to use a 80K (char[81920])buffer did not work and returns: So you've got some other bug in code you didn't show us. It's highly unlikely that you wouldn't be able to allocate an 80K buffer. (Whether that's big enough for your data even yet is a separate question.) What I was wondering was why you even bothered with the char[] buffer, when it looked like the actually useful return value was being accumulated in an expansible StringInfo buffer. regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 6: explain analyze is your friend
