No. It's debugging output for a problem we had earlier, and will be
removed before release.
thanks for clarifying. wasn't sure whether the comment in the release notes
really was applying to these "file not found" error messages.
Unless beaten to it, I'll try to look at the other part later
Joe Conway <[EMAIL PROTECTED]> writes:
> Sorry for the slow response -- I'm at the airport just heading home from
> a marathon 30 day business trip.
Yow. Hope you get some time off...
> Tom Lane wrote:
>> "Vitali Stupin" <[EMAIL PROTECTED]> writes:
>>> The error "invalid memory alloc request si
[offline ATM, can't look at the main issue, just wanted to get a comment
in about fopen(). Unless beaten to it, I'll try to look at the other
part later.]
> on a sidenote: are those fopen() errors debug-code-leftovers
> or something one should worry about? i can't find those files
> on the file
Just for your information.
Our problem was caused by a bad firmware of one of the harddisk in the
mirror.
"An HP ProLiant server configured with any of the Ultra320 hard drives
listed in Table 1 may experience an unsuccessful write operation when
transferring data to the hard drive during periods
Tom Lane wrote:
"Vitali Stupin" <[EMAIL PROTECTED]> writes:
The error "invalid memory alloc request size 4294967293" apears when
selecting array of empty arrays:
select ARRAY['{}'::text[],'{}'::text[]];
I can get a core dump off it too, sometimes. The problem is in
ExecEvalArray, which compu
