Re: Storage limits in PostgreSQL?

From: Lamar Owen <lamar(dot)owen(at)wgcr(dot)org>
To: Frank Hilliard <frankhilliard(at)home(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: Storage limits in PostgreSQL?
Date: 2001-06-25 17:32:17
Message-ID: 01062513321701.00958@lowen.wgcr.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Monday 25 June 2001 13:03, Frank Hilliard wrote:
> ACTION: copy 109,128 characters into a phpPgAdmin "Edit" text entry box.

> RESULT: phpPgAdmin cuts off the copy at 28,652 characters [no more
> accepted in box]
> UPDATE EMPTY text cell:
> RESULT: accepted [that is, it accepted 28,652 characters]

Most browsers only accept 32K in a text box. Netscape for sure accepts no
more than 32K. Plus, you have the webserver's POST limits to contend with.
With a web-based system it is often easy to forget that many limitations are
browser issues....I know I have forgotten about them in times past.

Don't know about PHP's string processing limits for sure, but I don't think
that's going to be an issue.

> QUERY cell with Cold Fusion
> RESULT: 7,995 characters displayed.

Sounds like a ColdFusion interface problem. How is the interface to
PostgreSQL handled? If in ODBC, is this the 7.1 ODBC driver? Is it an older
client lib?

> I can copy over 700,000 characters locally.

Then it's a client issue. Go over each and every link in the system -- to
test ODBC use some other client that can use ODBC to see what its limits are.

Work your way back to each client, layer by layer, and see where that lossage
comes from.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Gregory Wood 2001-06-25 17:34:37 Re: More Red Hat information
Previous Message Mitch Vincent 2001-06-25 17:22:43 Re: Storage limits in PostgreSQL?