| From: | Tsirkin Evgeny <tsurkin(at)mail(dot)jct(dot)ac(dot)il> |
|---|---|
| To: | Andrew Sullivan <andrew(at)libertyrms(dot)info>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: postgresql crushed with XLogWrite error |
| Date: | 2004-01-05 14:07:34 |
| Message-ID: | opr1a2uws4jbdarf@localhost |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Thanks!
Now another two questions:
Is there any official bug report on this that i can show to
my boss?
Should i upgrade to 7.3.4 to fix that bug or it is better to get newly
version?
What i need is to restore my corrupted db from the tape ,upgrade postgresql
(say from rpm) and just start the server.I don't want to do all the dump -
restore
thing.
On Mon, 5 Jan 2004 08:49:13 -0500, Andrew Sullivan
<andrew(at)libertyrms(dot)info> wrote:
> On Mon, Jan 05, 2004 at 02:14:37PM +0200, Tsirkin Evgeny wrote:
>> Hello dear list!
>> I am using postgresql 7.3.3 .Last night the errors occured.
> ^
>
>> by now ,but what happened?Is that a known bug?What to do next time?
>
> Yes, it's a known bug, and is the very reason 7.3.4 was released.
> Upgrade.
>
> A
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Sullivan | 2004-01-05 14:09:55 | Re: postgresql crushed with XLogWrite error |
| Previous Message | Andrzej Schulz | 2004-01-05 14:00:38 | Postgres & XML |