Followup to: Aborted Transaction During Vacuum

From: "G(dot) Anthony Reina" <reina(at)nsi(dot)edu>
To: "pgsql-hackers(at)postgreSQL(dot)org" <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Followup to: Aborted Transaction During Vacuum
Date: 1999-08-12 23:57:13
Message-ID: 37B35F59.EA3FEA33@nsi.edu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Here's a followup to my first message:

When I just try 'vacuum verbose' the vacuum goes through fine
without aborting the backend. So it appears to be a problem with
analyzing the optimizer indexing.

-Tony

================================================================

For those that missed my first message:

I've been getting a strange error from the vacuum command. When I try

'vacuum verbose analyze' the vacuum goes through the tables fine until

just after finishing one particular table. Then I get the error:

NOTICE: AbortTransaction and not in in-progress state

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.

When I try to vacuum the tables individually, I get no problems with

aborted backends.

Does anyone know what is going on here?

-Tony

Browse pgsql-hackers by date

  From Date Subject
Next Message Vadim Mikheev 1999-08-13 00:34:30 Re: [HACKERS] Re: We won!
Previous Message G. Anthony Reina 1999-08-12 23:33:32 Aborted Transaction During Vacuum