utsav.turray wrote:
>
> Dear Richard,
>
> I can't exclude the table because it is important table.
> Is there any way , i could get the data back.
Dump it and restore the dump.
--
Alvaro Herrerahttp://www.CommandPrompt.com/
The PostgreSQL Company - Command Promp
Dear Richard,
I can't exclude the table because it is important table.
Is there any way , i could get the data back.
Utsav
Richard Huxton wrote:
>
> utsav.turray wrote:
>> Dear All,
>>
>> I am using postgres 7.3 version on RHEL 4.0.
>> My database has been restored.
>> All tables all workin
utsav.turray wrote:
Dear All,
I am using postgres 7.3 version on RHEL 4.0.
My database has been restored.
All tables all working fine i.e select , update but on a particular table
its showing error
ERROR: XLogFlush: request AF/5703EDC8 is not satisfied --- flushed only to
AF/50F15ABC
I have s
Dear All,
I am using postgres 7.3 version on RHEL 4.0.
My database has been restored.
All tables all working fine i.e select , update but on a particular table
its showing error
ERROR: XLogFlush: request AF/5703EDC8 is not satisfied --- flushed only to
AF/50F15ABC
I have searched other threads
general
Subject: Re: [GENERAL] ERROR: XLogFlush: request
On Fri, 2007-04-13 at 10:10, Nitin Verma wrote:
> Thanx Tom, anyway we are moving to 8.1.0 soon.
>
> Leaving that moving all our client to newer release will take sometime. I
> hope you know how it works in a product. Till that time we
On Fri, 2007-04-13 at 10:10, Nitin Verma wrote:
> Thanx Tom, anyway we are moving to 8.1.0 soon.
>
> Leaving that moving all our client to newer release will take sometime. I
> hope you know how it works in a product. Till that time we need to release a
> patch that recovers from this condition.
>
me on a lower risk of getting in
this situation?
-Original Message-
From: Alvaro Herrera [mailto:[EMAIL PROTECTED]
Sent: Friday, April 13, 2007 8:59 PM
To: Nitin Verma
Cc: Tom Lane; [EMAIL PROTECTED]
Subject: Re: [GENERAL] ERROR: XLogFlush: request
Nitin Verma wrote:
> Thanx Tom, any
Nitin Verma wrote:
> Thanx Tom, anyway we are moving to 8.1.0 soon.
>
> Leaving that moving all our client to newer release will take sometime. I
> hope you know how it works in a product. Till that time we need to release a
> patch that recovers from this condition.
>
> Said that, do we have som
y use of or Is it safe to restart postmaster at this time?
What all should be done when this happened? Any suggestions.
=
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]
Sent: Friday, April 13, 2007 8:18 PM
To: Nitin Verma
Cc: [EMAIL PROTECTED]
Subject: Re: [G
"Nitin Verma" <[EMAIL PROTECTED]> writes:
> xlog.c code from version we use (7.3.2)
> ...
> What all should be done when this happened? Any suggestions.
Updating to something newer than 7.3.2 would seem to be a good idea.
7.3.18 is the current release in that branch.
regar
Hi All,
xlog.c code from version we use (7.3.2)
/*
* If we still haven't flushed to the request point then we have a
* problem; most likely, the requested flush point is past end of
* XLOG. This has been seen to occur when a disk page has a corrupted
*
java.sql.SQLException: ERROR: XLogFlush: request
0/240169BC is not satisfied --- flushed only to 0/23FFC01C
This error I was in the logs of a java process that was failing to get some
data. But using psql I was able to connect and query all the data. Thus this
may indicate some connection / state
12 matches
Mail list logo
