From: | "Rajan Bhide" <rbhide(at)nulinkinc(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <pgsql-novice(at)postgresql(dot)org> |
Cc: | "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Subject: | Re: Error msgs from PostgreSQL server : specified item offset is too large, failed to add item to the page |
Date: | 2004-06-03 14:35:16 |
Message-ID: | FF851C7EEB75954F9BCFB5CA117AB1ECFC3237@delta.nulinkinc.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
> I've looked at the code fairly carefully and I don't see how this
could happen. Can you provide a self-contained test case that makes it
happen?
I would try to build a test program. Currently this is happening with my
production app on longevity run.
But still would like to know the reason to get such error. Any Postgres
document or other links would be helpful.
Is there any help from the stat stuff provided in the earliar mail?
Any fine tuning or changes in postgresql.conf file required?
My app makes 18 conncurrent connection with the Postgres server?
I was using periodic reindexing, but that too did'nt helped much, so I
have disbled it again. Jes doing VACCUM ANALYSE on every table after
every 10 mins.
BTW the source code was compiled on SunOS5.8 using Sun Forte's cc
compiler:
/configure --prefix=/usr/local/pgsql --enable-thread-safety
--without-readline CFLAGS='-D_REENTRANT' CPPFLAGS='-mt'
cc=/export/home/uxapps/workshop/SUNWspro/bin/cc
Does this helps?
Thanks,
Rajan Bhide
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-06-03 14:43:31 | Re: Error msgs from PostgreSQL server : specified item offset is too large, failed to add item to the page |
Previous Message | Tom Lane | 2004-06-03 14:19:03 | Re: Error msgs from PostgreSQL server : specified item offset is too large, failed to add item to the page |