Re: literal limits in 8.3

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Greg Sabino Mullane" <greg(at)turnstep(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: literal limits in 8.3
Date: 2008-11-24 20:58:23
Message-ID: 5786.1227560303@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

"Greg Sabino Mullane" <greg(at)turnstep(dot)com> writes:
>> What it boils down to is lack of error checking in psql (not the
>> backend).

> What is it about certain boxes that causes the failure, but not on others?

It's a matter of having the out-of-memory condition occur just at the
wrong step, ie, the output from psql's lexical scan (as opposed to the
input, or when trying to construct the Query message to send to the
backend). So it would depend on factors like 32-vs-64-bit and what
you had ulimit set to.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Vishal Arora 2008-11-25 06:47:33 Re: PgAgent Job Scehduler is NOT running
Previous Message Sam Mason 2008-11-24 20:14:40 Re: [GENERAL] literal limits in 8.3

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2008-11-24 21:11:03 Re: WIP: default values for function parameters
Previous Message Sam Mason 2008-11-24 20:14:40 Re: [GENERAL] literal limits in 8.3