From: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
---|---|
To: | German Becker <german(dot)becker(at)gmail(dot)com>, Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: PANIC during VACUUM |
Date: | 2013-04-30 11:51:23 |
Message-ID: | 1367322683.44994.YahooMailNeo@web162902.mail.bf1.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
[please don't top-post]
German Becker <german(dot)becker(at)gmail(dot)com> wrote:
> Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> wrote:
>> German Becker wrote:
>>> I am testing version 9.1.9 before putting it in production. One
>>> of my tests involved deleting a the contents of a big table ( ~
>>> 13 GB size) and then VACUUMing it. During VACUUM PANICS.
>> If you mess with the database files, errors like this are to be
>> expected.
> Thanks for your reply. In which sense did I mess with the
> database files?
You didn't say how you deleted the contents of that big table, and
it appears that Albe assumed you deleted or truncated the
underlying disk file rather than using the DELETE or TRUNCATE SQL
statement.
In any event, more details would help people come up with ideas on
what might be wrong.
http://wiki.postgresql.org/wiki/Guide_to_reporting_problems
--
Kevin Grittner
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Albe Laurenz | 2013-04-30 12:08:25 | Re: PANIC during VACUUM |
Previous Message | German Becker | 2013-04-30 11:46:22 | Re: PANIC during VACUUM |