From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | Christine Penner <christine(at)ingenioussoftware(dot)com> |
Cc: | Postgres-General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Restore Crashes Postgres |
Date: | 2009-04-28 19:10:19 |
Message-ID: | dcc563d10904281210g53403b4co689a050a96b066f9@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, Apr 28, 2009 at 11:56 AM, Christine Penner
<christine(at)ingenioussoftware(dot)com> wrote:
> The crashes I get are the windows, this program has encountered a problem
> and must close, error. At that point I can't do anything with Postgres. I
> can't restart the service. I have to restart windows.
>
> Usually we are restoring into an already loaded database but we have gotten
> the crashes loading into a new (empty) database. I don't think its parent
> child issues. The only constraints we have are for the primary key's. Also,
> I'm told it doesn't matter but I always make sure I don't have the database
> open when I create a backup.
>
> I'm wondering if there is a better way to do a backup and restore. I'm
> really worried that we are going to have a client need a backup and not be
> able to load it. Before we release it to clients we will be using a command
> line to do the backup and restore but I'm pretty sure it's the same thing as
> running it through pgAdmin.
I'm really starting to wonder about your hardware and / or OS. Are
you running any anti-virus software (if so turn it off and / or
uninstall it)? Have you tested your machine with something like
memtest86+?
From | Date | Subject | |
---|---|---|---|
Next Message | Carlo Stonebanks | 2009-04-28 19:29:29 | Re: UPDATE... FROM - will ORDER BY not respected? |
Previous Message | Alvaro Herrera | 2009-04-28 18:35:21 | Re: Restore Crashes Postgres |