pg.ddx.io pgsql-interfaces@postgresql.org mailing list archivehelp / color / mirror / Atom feed
problem when vacuuming. . . 2+ messages / 2 participants [nested] [flat]
* problem when vacuuming. . . @ 1999-04-19 22:24 JT Kirkpatrick <jt-kirkpatrick@mpsllc.com> 1999-04-20 13:17 ` Re: [GENERAL] problem when vacuuming. . . Karl DeBisschop <kdebisschop@spaceheater.infoplease.com> 0 siblings, 1 reply; 2+ messages in thread From: JT Kirkpatrick @ 1999-04-19 22:24 UTC (permalink / raw) To: 'pgsql-admin@hub.org' <pgsql-admin@hub.org>; 'pgsql-sql@hub.org' <pgsql-sql@hub.org>; 'pgsql-general@hub.org' <pgsql-general@hub.org>; 'pgsql-interfaces@hub.org' <pgsql-interfaces@hub.org> When I vacuum I get two messages: NOTICE: Index pg_class_relname_index: NUMBER OF INDEX' TUPLES (108) IS NOT THE SAME AS HEAP' (82) NOTICE: Index pg_class_oid_index: NUMBER OF INDEX' TUPLES (108) IS NOT THE SAME AS HEAP' (82) I had followed some advice I read in one of these postgres mailing lists (from this weekend) regarding case problems when transferring from access97, and I executed both of those updates. I can't find them now, nor can I remember them, but they replaced certain values in the tables corresponding to the indexes above with the lowercase equivalent of those values. I'd like to try to reverse the effect - does anyone have a copy of that email from sometime this weekend? jt ^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: [GENERAL] problem when vacuuming. . . 1999-04-19 22:24 problem when vacuuming. . . JT Kirkpatrick <jt-kirkpatrick@mpsllc.com> @ 1999-04-20 13:17 ` Karl DeBisschop <kdebisschop@spaceheater.infoplease.com> 0 siblings, 0 replies; 2+ messages in thread From: Karl DeBisschop @ 1999-04-20 13:17 UTC (permalink / raw) To: jt-kirkpatrick@mpsllc.com; +Cc: pgsql-admin@hub.org; pgsql-sql@hub.org; pgsql-general@hub.org; pgsql-interfaces@hub.org For what it's worth, my experience with this error is that your backend crashed during the update - why it should do that on such a small set of data, I cannot begin to guess. But I have always found the data to be okay, though the query executing at the time will need to be completed. Just drop the indexes, complete the query, and recreate the indexes (I suggets this order for performance reasons, unless your update depends on using the indexes to perform efficiently). You may also want to increase the amount of memory allocated to the backend, both -B and -S (buffers, and sort buffers) From: JT Kirkpatrick <jt-kirkpatrick@mpsllc.com> Date: Mon, 19 Apr 1999 18:24:16 -0400 Organization: MPS, LLC Content-Type: text/plain; charset="us-ascii" Sender: owner-pgsql-general@postgreSQL.org Precedence: bulk When I vacuum I get two messages: NOTICE: Index pg_class_relname_index: NUMBER OF INDEX' TUPLES (108) IS NOT THE SAME AS HEAP' (82) NOTICE: Index pg_class_oid_index: NUMBER OF INDEX' TUPLES (108) IS NOT THE SAME AS HEAP' (82) I had followed some advice I read in one of these postgres mailing lists (from this weekend) regarding case problems when transferring from access97, and I executed both of those updates. I can't find them now, nor can I remember them, but they replaced certain values in the tables corresponding to the indexes above with the lowercase equivalent of those values. I'd like to try to reverse the effect - does anyone have a copy of that email from sometime this weekend? jt -- Karl DeBisschop <kdebisschop@spaceheater.infoplease.com> 617.832.0332 (Fax: 617.956.2696) Information Please - your source for FREE online reference http://www.infoplease.com - Your Ultimate Fact Finder http://kids.infoplease.com - The Great Homework Helper ^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~1999-04-20 13:17 UTC | newest] Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 1999-04-19 22:24 problem when vacuuming. . . JT Kirkpatrick <jt-kirkpatrick@mpsllc.com> 1999-04-20 13:17 ` Karl DeBisschop <kdebisschop@spaceheater.infoplease.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions for how to clone and mirror all data and code used for this inbox