> I'm a bit late with my reaction but I've seen the message below on a Cobalt
> system (kernel 2.0.34) with
> postgresql 6.5.3.
>
> The problem could be reproduced (the entire /var/lib/pgsql dir would be
> replaced after every crash).
> A PHP3 script revoking user rights on many tables and ending
I'm a bit late with my reaction but I've seen the message below on a Cobalt
system (kernel 2.0.34) with
postgresql 6.5.3.
The problem could be reproduced (the entire /var/lib/pgsql dir would be
replaced after every crash).
A PHP3 script revoking user rights on many tables and ending with a vacuum
Bruce Momjian wrote:
>
> > Bruce Momjian wrote:
> >
> > > > Anyone seen this message or know what it means?
> > > >
> > > > NOTICE: Index pg_proc_prosrc_index: NUMBER OF INDEX' TUPLES (1071) IS
> > > > NOT THE SAME AS HEAP' (1070)
> > >
> > > Drop index and recreate. Next release will be more s
Bruce Momjian wrote:
> > > I think it is harmless. To fix it properly requires a
> > > very sophisticated write-ahead log that is scheduled for 7.1 in about
> > > six months.
> >
> > This problem stops my psql dead in its tracks for related queries even across new
> > sessions. Requires a rebu
> > I think it is harmless. To fix it properly requires a
> > very sophisticated write-ahead log that is scheduled for 7.1 in about
> > six months.
>
> This problem stops my psql dead in its tracks for related queries even across new
> sessions. Requires a rebuild of indices before any queries
Bruce Momjian wrote:
> > Is the problem well-understood? Is there a place where I can read up on it? This
> > kind of instability is painful enough to get me thinking about trying to hack my
> > distribution...
>
> I believe it has to do with extra index tuples showing up in the index
> that ar
> Bruce Momjian wrote:
>
> > > > That will also be fixed.
> > >
> > > Do you mean to say the offending index will be auto-corrected on the fly? That
> > > would be almost as good as preventing the root cause in the first place...
> >
> > No, it just reports the index name. In 7.1, I think this
Bruce Momjian wrote:
> > > That will also be fixed.
> >
> > Do you mean to say the offending index will be auto-corrected on the fly? That
> > would be almost as good as preventing the root cause in the first place...
>
> No, it just reports the index name. In 7.1, I think this problem will
> g
> > That will also be fixed.
>
> Do you mean to say the offending index will be auto-corrected on the fly? That
> would be almost as good as preventing the root cause in the first place...
No, it just reports the index name. In 7.1, I think this problem will
go away, if not in 7.0.
--
Bruc
Bruce Momjian wrote:
> > Bruce Momjian wrote:
> >
> > > > Anyone seen this message or know what it means?
> > > >
> > > > NOTICE: Index pg_proc_prosrc_index: NUMBER OF INDEX' TUPLES (1071) IS
> > > > NOT THE SAME AS HEAP' (1070)
> > >
> > > Drop index and recreate. Next release will be more spe
> Bruce Momjian wrote:
>
> > > Anyone seen this message or know what it means?
> > >
> > > NOTICE: Index pg_proc_prosrc_index: NUMBER OF INDEX' TUPLES (1071) IS
> > > NOT THE SAME AS HEAP' (1070)
> >
> > Drop index and recreate. Next release will be more specific in error
> > message.
>
> I ha
11 matches
Mail list logo
