From: | "Gurjeet Singh" <singh(dot)gurjeet(at)gmail(dot)com> |
---|---|
To: | taskew(at)demandforesight(dot)com |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: Internal Error XXOO...Mission Critical |
Date: | 2006-12-22 07:13:10 |
Message-ID: | 65937bea0612212313r432141f0t70c8e45ec30fbce8@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
The community will need more details to move forward. Please read the
following mail; it is a good guide to how to post queries to get answers and
responses quickly.
http://archives.postgresql.org/pgsql-performance/2004-06/msg00235.php
Be a better student, ask good questions :)
Good luck.
On 12/21/06, Terry Askew <taskew(at)demandforesight(dot)com> wrote:
>
> Postgres continues to hang while we attempt to dump tables after several
> successful dumps. Is this a memory issue. Where is the data being dumped
> to…Is it being temporarily stored in some repository that can only handle so
> much data before it produces an exception message.
>
>
>
> This is critical in that our user community has all but lost faith in our
> software.
>
>
>
> We run a batch process right before data profiles are being created at
> which point Postgres stalls, and the batch process completes perfectly every
> night.
>
>
>
> This will obviously affect any user attempting to iteratively delete large
> quantities of data before performing the next operation.
>
>
>
> Please Help….Willing to do whatever it takes to resolve this issue, and I
> assure you that it will increase the stability of Postgres.
>
>
>
> Sincerely,
>
>
>
> Terry Askew
>
> Foresight Technologies, LLC.
>
> Executive VP, Software Development
>
> 770-656-9876
>
--
gurjeet[(dot)singh](at)EnterpriseDB(dot)com
singh(dot)gurjeet(at){ gmail | hotmail | yahoo }.com
From | Date | Subject | |
---|---|---|---|
Next Message | Gurjeet Singh | 2006-12-22 08:03:15 | Re: BUG #2847: Bug with IN statement |
Previous Message | Bernd Helmle | 2006-12-21 21:18:01 | Re: BUG #2850: Cannot select from information_schema.schemat |