| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | oberpwd(at)anubis(dot)network(dot)com (Wade D(dot) Oberpriller) |
| Cc: | pgsql-general(at)postgresql(dot)org (general-help postgresql) |
| Subject: | Re: Increased BLKSZ, but now pgsql seg-faults? |
| Date: | 2000-09-28 01:38:05 |
| Message-ID: | 19581.970105085@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
oberpwd(at)anubis(dot)network(dot)com (Wade D. Oberpriller) writes:
> I've increased the BLKSZ to 32K to support large tuples and then I did
> a full re-compile (gmake clean, configure, gmake all, gmake install)
> and the database accepts my large tuples. But now when I come in
> through psql, I get a segmentation fault inside of psql when I try to
> display the table with the large tuples (i.e. \d largetable).
In psql? That's pretty odd -- psql shouldn't even be able to determine
what blocksize the server is using, much less be affected by it. I
suspect you may have unearthed an unrelated bug.
Would you (re)compile psql with -g and send a stack trace of the fault?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | elein | 2000-09-28 01:40:56 | oracle ate |
| Previous Message | mjp | 2000-09-28 00:53:11 | Re: full text indexing |