Re: Storage limits in PostgreSQL?
От | Lamar Owen |
---|---|
Тема | Re: Storage limits in PostgreSQL? |
Дата | |
Msg-id | 01062513321701.00958@lowen.wgcr.org обсуждение исходный текст |
Ответ на | Storage limits in PostgreSQL? (Frank Hilliard <frankhilliard@home.com>) |
Список | 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
В списке pgsql-general по дате отправления: