| From: | Ken Corey <ken(at)kencorey(dot)com> |
|---|---|
| To: | Ian Lance Taylor <ian(at)airs(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-novice(at)postgresql(dot)org" <pgsql-novice(at)postgresql(dot)org> |
| Subject: | Re: Re: Yikes! Bitten by line length? |
| Date: | 2001-01-18 23:13:29 |
| Message-ID: | 3A677899.D0AC1392@kencorey.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
Ian Lance Taylor wrote:
> I very much doubt it is the fgets function.
>
> I suspect it is the terminal driver. The terminal driver only hands
> data back to the application when it sees a newline. It probably only
> holds 256 characters.
>
> Try using an editor to create a file with a line longer than 256
> characters, and run `test < file', to see whether it is fgets or the
> terminal driver.
You're exactly on the money. Thanks. Where were you this morning?
*smile*
Since a partiularly long SQL query was the first time I'd seen this kind
of a problem (and others might see it), perhaps it still deserves a
paragraph in the FAQ, even though it has *nothing* to do with postgreSQL
directly?
-Ken
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ian Lance Taylor | 2001-01-18 23:15:02 | Re: Re: Yikes! Bitten by line length? |
| Previous Message | Ken Corey | 2001-01-18 23:05:07 | Argh! What's a 'bpchar'? (copy/serial issues...I think) |