pg.ddx.io pgsql-sql@postgresql.org mailing list archivehelp / color / mirror / Atom feed
VACUUM PROBLEM 2+ messages / 2 participants [nested] [flat]
* VACUUM PROBLEM @ 1999-12-01 05:40 Dipankar Chakrabarti <dipanc@yahoo.com> 1999-12-01 16:19 ` Re: [SQL] VACUUM PROBLEM Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 1 reply; 2+ messages in thread From: Dipankar Chakrabarti @ 1999-12-01 05:40 UTC (permalink / raw) To: pgsql-sql@hub.org Dear All, I am having problem while doing vacuum. The error message is as follows: NOTICE: Rel queuestatval: Pages: 2 --> 1; Tuple(s) moved: 16. Elapsed 0/0 sec. NOTICE: BlowawayRelationBuffers(queuestatval, 1): block 1 is referenced (private 0, last 0, global 1) pqReadData() -- backend closed the channel unexpectedly. This probably means the backend terminated abnormally before or while processing the request. We have lost the connection to the backend, so further processing is impossible. Terminating. ----------------------------------------- I am unable to find head or tail about it. NEED HELP!! I am using PostgerSQL 6.5.2 on LINUX 6.0. Regards, Dipankar Chakrabarti Senior Manager - Projects Mindteck (I) Ltd. __________________________________________________ Do You Yahoo!? Thousands of Stores. Millions of Products. All in one place. Yahoo! Shopping: http://shopping.yahoo.com ^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: [SQL] VACUUM PROBLEM 1999-12-01 05:40 VACUUM PROBLEM Dipankar Chakrabarti <dipanc@yahoo.com> @ 1999-12-01 16:19 ` Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 2+ messages in thread From: Tom Lane @ 1999-12-01 16:19 UTC (permalink / raw) To: Dipankar Chakrabarti <dipanc@yahoo.com>; +Cc: pgsql-sql@hub.org Dipankar Chakrabarti <dipanc@yahoo.com> writes: > I am having problem while doing vacuum. > The error message is as follows: > NOTICE: Rel queuestatval: Pages: 2 --> 1; Tuple(s) > moved: 16. Elapsed 0/0 sec. > NOTICE: BlowawayRelationBuffers(queuestatval, 1): > block 1 is referenced (private 0, last 0, global 1) > pqReadData() -- backend closed the channel > unexpectedly. This probably means the backend > terminated abnormally before or while processing the > request. If you look in the postmaster log file, you should find additional info about the crash. 6.5.* libpq has a bug that makes it discard the last backend error message if it sees an unexpected channel closure :-(. So there is probably at least one error message that you're not seeing on the client side --- but it should be there in the log file. regards, tom lane ^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~1999-12-01 16:19 UTC | newest] Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 1999-12-01 05:40 VACUUM PROBLEM Dipankar Chakrabarti <dipanc@yahoo.com> 1999-12-01 16:19 ` Tom Lane <tgl@sss.pgh.pa.us>
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