On Thu, Sep 26, 2013 at 4:19 PM, David Rennalls wrote:
> On Thu, Sep 26, 2013 at 3:40 PM, Kim Applegate wrote:
>> I have seen this issue on a slave although it was in version 9.2. I ran
>
> oh ok. Looks like the issue was fixed in 8.2.23 according to these
> release notes http://www.postgresql.o
On Thu, Sep 26, 2013 at 3:40 PM, Kim Applegate wrote:
> I have seen this issue on a slave although it was in version 9.2. I ran
oh ok. Looks like the issue was fixed in 8.2.23 according to these
release notes http://www.postgresql.org/docs/8.2/static/release-8-2-23.html
...
o Fix race condition
I have seen this issue on a slave although it was in version 9.2. I ran
this
select 2619::regclass;
regclass
--
pg_statistic
(1 row)
I was able to fix my select issue by running analyze on the database
On Thu, Sep 26, 2013 at 11:47 AM, David Rennalls wrote:
> David Fetter
David Fetter fetter.org> writes:
>
> Upgrade to 9.1.3 and let us know whether that fixes the problem.
I've run into this issue as well on postgres 8.4.14. Aside from upgrading to a
newer release is there any manual fixup that can be done ?
Thanks,
David
--
Sent via pgsql-bugs mailing
leo xu writes:
>i see a lot ,"missing chunk number 0 for toast value 96635 in
> pg_toast_2619",," in background aler log.select * from iclock ,no data
> retrun,indicate missing chunk number 0 for toast value 96635 in
> pg_toast_2619.
There is a known bug that can cause that symptom, but
hello:
i see a lot ,"missing chunk number 0 for toast value 96635 in
pg_toast_2619",," in background aler log.select * from iclock ,no data
retrun,indicate missing chunk number 0 for toast value 96635 in
pg_toast_2619.
i use pg_dump table,then truncate table,then pg_dump it current
data
