From: | Celia McInnis <celia(dot)mcinnis(at)gmail(dot)com> |
---|---|
To: | Juan José Santamaría Flecha <juanjo(dot)santamaria(at)gmail(dot)com> |
Cc: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Trouble after crashing postgresql |
Date: | 2021-02-26 13:07:32 |
Message-ID: | CAGD6t7JhVaocX5Lfc1gSJegKLeQ1cwt7fKOHy_8wL2OBHJ86JA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Alas I didn't bother making a backup since It is a research database. Still
it is large enough that I'd rather not do a dump/restore now of the tables
that I'd want to dump/restore. Is there some other neat alternative that I
can do to just terminate postgresql's attempt to clean up after I messed it
up? BTW I don't know the name of the table that it was trying to create
since my stored procedure had generated a name starting with "tmp" and
having a time stamp and other info after that. Originally I was using a
temporary table, but had made it permanent to help debug...
On Fri, Feb 26, 2021 at 7:46 AM Juan José Santamaría Flecha <
juanjo(dot)santamaria(at)gmail(dot)com> wrote:
>
> On Fri, Feb 26, 2021 at 9:15 AM Celia McInnis <celia(dot)mcinnis(at)gmail(dot)com>
> wrote:
>
>>
>> Help! Is there some way to have the system come up without trying to
>> restore the state that it was in when I crashed the system? The tables that
>> were being formed are not of any use to me.
>>
>
> What you are trying to achieve sounds like restoring a backup, do you have
> any available?
>
> Regards,
>
> Juan José Santamaría Flecha
>
From | Date | Subject | |
---|---|---|---|
Next Message | Wells Oliver | 2021-02-26 18:01:21 | Eternal DataFileRead on partition seeks after upgrade? Or in general.. |
Previous Message | Juan José Santamaría Flecha | 2021-02-26 12:43:46 | Re: Trouble after crashing postgresql |