Thread: writing block 6850 of relation 1663/17231/1259
Sorry forgot to change title. Any help will be greatly received! -----Original Message----- From: Mudit Mishra Sent: 11 September 2011 14:39 To: pgsql-general@postgresql.org Subject: RE: [GENERAL] COPY FROM (query) in plpgsql Hi All, Can anyone help me to fix this issue? I keep getting following errors in the log. I do not have a backup of the database and want to recover the database as muchas possible from this error. 2011-09-09 11:06:39 PANIC: xlog flush request 2/190490D8 is not satisfied --- flushed only to 2/19004190 2011-09-09 11:06:39 CONTEXT: writing block 6850 of relation 1663/17231/1259 OS: Windows 2003 server pgsql version: Welcome to psql 8.0.3, the PostgreSQL interactive terminal. Thanks, Mudit
Mudit Mishra wrote: > Sorry forgot to change title. > > Any help will be greatly received! > > > -----Original Message----- > From: Mudit Mishra > Sent: 11 September 2011 14:39 > To: pgsql-general@postgresql.org > Subject: RE: [GENERAL] COPY FROM (query) in plpgsql > > Hi All, > > Can anyone help me to fix this issue? > > I keep getting following errors in the log. I do not have a backup of the database and want to recover the database asmuch as possible from this error. > > 2011-09-09 11:06:39 PANIC: xlog flush request 2/190490D8 is not satisfied --- flushed only to 2/19004190 > 2011-09-09 11:06:39 CONTEXT: writing block 6850 of relation 1663/17231/1259 > > > OS: Windows 2003 server > pgsql version: > Welcome to psql 8.0.3, the PostgreSQL interactive terminal. FYI, that is a very old version of Postgres and you have not even minor-upgraded it in years. -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. +
Thanks Bruce. If I upgrade the pg sql will it fix the problem - quite happy to do if it does. Else need way to recover thedatabase. After some googling I found that 1259 represents PG_CLASS table. This drift me towards the conclusion that this table isin unstable state. I have run pg_resetxlog couple of times without any switches like -o,-x,-l and it has not helped. I'm going to run it againwith switches and see how it goes. Thanks, Mudit -----Original Message----- From: Bruce Momjian [mailto:bruce@momjian.us] Sent: 12 September 2011 02:37 To: Mudit Mishra Cc: pgsql-general@postgresql.org Subject: Re: [GENERAL] writing block 6850 of relation 1663/17231/1259 Mudit Mishra wrote: > Sorry forgot to change title. > > Any help will be greatly received! > > > -----Original Message----- > From: Mudit Mishra > Sent: 11 September 2011 14:39 > To: pgsql-general@postgresql.org > Subject: RE: [GENERAL] COPY FROM (query) in plpgsql > > Hi All, > > Can anyone help me to fix this issue? > > I keep getting following errors in the log. I do not have a backup of the database and want to recover the database asmuch as possible from this error. > > 2011-09-09 11:06:39 PANIC: xlog flush request 2/190490D8 is not > satisfied --- flushed only to 2/19004190 > 2011-09-09 11:06:39 CONTEXT: writing block 6850 of relation > 1663/17231/1259 > > > OS: Windows 2003 server > pgsql version: > Welcome to psql 8.0.3, the PostgreSQL interactive terminal. FYI, that is a very old version of Postgres and you have not even minor-upgraded it in years. -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. +
It probably won't fix it, but you'll avoid possible issues in the future. However you should look at possibly upgrading to 8.4 or later, as 8.0 is either out of its support life, or getting close to it.
On 11/09/2011 10:37 PM, Mudit Mishra wrote: > Can anyone help me to fix this issue? > > I keep getting following errors in the log. I do not have a backup of the database and want to recover the database asmuch as possible from this error. > > 2011-09-09 11:06:39 PANIC: xlog flush request 2/190490D8 is not satisfied --- flushed only to 2/19004190 > 2011-09-09 11:06:39 CONTEXT: writing block 6850 of relation 1663/17231/1259 Before you do ANYTHING else, copy your data directory to other storage. Do not try to "fix" anything until you have made a copy of your data directory. Copy it while the server is stopped. -- Craig Ringer