Re: [ADMIN] Crash with data corruption under Windows

2009-02-23 Thread Nicola Mauri
Messaggio Originale Oggetto: Re: [ADMIN] Crash with data corruption under Windows Da: Scott Marlowe On Mon, Feb 23, 2009 at 9:49 AM, Nicola Mauri wrote: Messaggio Originale Oggetto: Re: [ADMIN] Crash with data corruption under Windows Da: Scott

Re: [ADMIN] Crash with data corruption under Windows

2009-02-23 Thread Scott Marlowe
On Mon, Feb 23, 2009 at 9:49 AM, Nicola Mauri wrote: > > Messaggio Originale > Oggetto: Re: [ADMIN] Crash with data corruption under Windows > Da: Scott Marlowe >> >> Usually when I see the permission denied thing there's anti-virus >> softw

Re: [ADMIN] Crash with data corruption under Windows

2009-02-23 Thread Nicola Mauri
Messaggio Originale Oggetto: Re: [ADMIN] Crash with data corruption under Windows Da: Scott Marlowe Usually when I see the permission denied thing there's anti-virus software hard locking pgsql files in the middle of the day. Have you experienced data loss too in

Re: [ADMIN] Crash with data corruption under Windows

2009-02-23 Thread Nicola Mauri
On Fri, Feb 20, 2009 at 03:32:16PM +0100, Nicola Mauri wrote: We run into the following issue with Windows 2003 and Postgres 8.2.6 while database was running: FATAL: "pg_tblspc/16405/37638" is not a valid data directory DETAIL: File "pg_tblspc/16405/37638/PG_VERSION" is missing. ER

Re: [ADMIN] Crash with data corruption under Windows

2009-02-20 Thread Scott Marlowe
On Fri, Feb 20, 2009 at 7:32 AM, Nicola Mauri wrote: > > We run into the following issue with Windows 2003 and Postgres 8.2.6 while > database was running: > > FATAL: "pg_tblspc/16405/37638" is not a valid data directory > DETAIL: File "pg_tblspc/16405/37638/PG_VERSION" is missing. > ERROR:

Re: [ADMIN] Crash with data corruption under Windows

2009-02-20 Thread Kenneth Marshall
On Fri, Feb 20, 2009 at 03:32:16PM +0100, Nicola Mauri wrote: > > We run into the following issue with Windows 2003 and Postgres 8.2.6 while > database was running: > > FATAL: "pg_tblspc/16405/37638" is not a valid data directory > DETAIL: File "pg_tblspc/16405/37638/PG_VERSION" is missing.

[ADMIN] Crash with data corruption under Windows

2009-02-20 Thread Nicola Mauri
We run into the following issue with Windows 2003 and Postgres 8.2.6 while database was running: FATAL: "pg_tblspc/16405/37638" is not a valid data directory DETAIL: File "pg_tblspc/16405/37638/PG_VERSION" is missing. ERROR: could not open relation 16405/37638/2661: No such file or d

Re: [ADMIN] Crash with pg_clog file not found

2008-11-03 Thread Scott Marlowe
On Mon, Nov 3, 2008 at 8:49 AM, Matthieu Roger <[EMAIL PROTECTED]> wrote: > > 8.3.3 was also producing the same error, prior version (8.3.1) did not > seem to exhibit it, though we've opened a new universe in the web game > which increased the number of accounts and players in september so > maybe

Re: [ADMIN] Crash with pg_clog file not found

2008-11-03 Thread Matthieu Roger
2008/11/3 Tom Lane <[EMAIL PROTECTED]>: > "Matthieu Roger" <[EMAIL PROTECTED]> writes: >> 2008-10-31 20:14:27 CET 10.0.0.119 exile PANIC: could not access >> status of transaction 0 > > Can you present a self-contained test case that causes that? Hello Tom, we were not able to reproduce at will

Re: [ADMIN] Crash with pg_clog file not found

2008-11-03 Thread Tom Lane
"Matthieu Roger" <[EMAIL PROTECTED]> writes: > 2008-10-31 20:14:27 CET 10.0.0.119 exile PANIC: could not access > status of transaction 0 Can you present a self-contained test case that causes that? A stack trace from the PANIC would be mighty useful too, but I dunno whether there's any point in

Re: [ADMIN] Crash with pg_clog file not found

2008-11-03 Thread Matthieu Roger
>>2008-10-31 20:17:32 CET 10.0.0.119 exile FATAL: connection limit >>exceeded for non-superusers > > This is just a wild guess, but how many connections are there? Especially see This link is interesting, I'm reading about it and found a good article on the msdn blog with a tool to check the desk

Re: [ADMIN] Crash with pg_clog file not found

2008-11-03 Thread Rainer Bauer
"Matthieu Roger" wrote: >2008-10-31 20:17:32 CET 10.0.0.119 exile FATAL: connection limit >exceeded for non-superusers This is just a wild guess, but how many connections are there? Especially see

[ADMIN] Crash with pg_clog file not found

2008-11-02 Thread Matthieu Roger
Hello, OS: Windows 2003 64bits Cpu : 2x Opteron Dual core Ram : 8Go Ram Disk : Areca Raid10 6x 200Go sata Postgresql 8.3.4 we're experiencing problems since some weeks with always the same error (same transaction 0 and same pg_clog file ) : 2008-10-31 20:14:27 CET 10.0.0.119 exile PANIC: co

Re: [ADMIN] crash help, pgsql 7.2.1 on RH7.3

2002-11-23 Thread Tom Lane
Lamar Owen <[EMAIL PROTECTED]> writes: > On Saturday 23 November 2002 12:10, Tom Lane wrote: >> Yup, you would. I'd recommend building from source so that you can add >> both --enable-debug and --enable-cassert to the configure flags. (It >> may actually be possible to do that with the SRPM distr

Re: [ADMIN] crash help, pgsql 7.2.1 on RH7.3

2002-11-23 Thread Lamar Owen
On Saturday 23 November 2002 12:10, Tom Lane wrote: > "Tim Lynch" <[EMAIL PROTECTED]> writes: > > but, uh, what am i going to do with a core file? i would need a > > non-stripped postgres binary first, right? > Yup, you would. I'd recommend building from source so that you can add > both --enable

Re: [ADMIN] crash help, pgsql 7.2.1 on RH7.3

2002-11-23 Thread Tom Lane
"Tim Lynch" <[EMAIL PROTECTED]> writes: > but, uh, what am i going to do with a core file? i would need a non-stripped > postgres binary first, right? Yup, you would. I'd recommend building from source so that you can add both --enable-debug and --enable-cassert to the configure flags. (It may a

Re: [ADMIN] crash help, pgsql 7.2.1 on RH7.3

2002-11-22 Thread Lamar Owen
On Thursday 21 November 2002 20:05, Tim Lynch wrote: > increase their ulimits - call me old fasioned... what's next, regular user > negative renice?!? anyways... Actually yes. > but, uh, what am i going to do with a core file? i would need a > non-stripped postgres binary first, right? If yo

Re: [ADMIN] crash help, pgsql 7.2.1 on RH7.3

2002-11-22 Thread Tim Lynch
Wednesday, November 20, 2002 8:31 PM Subject: Re: [ADMIN] crash help, pgsql 7.2.1 on RH7.3 : I said: : > "Tim Lynch" <[EMAIL PROTECTED]> writes: : >> i don't see a core file. : : > Check that you are starting the postmaster with "ulimit -c unlimited"; : >

Re: [ADMIN] crash help, pgsql 7.2.1 on RH7.3

2002-11-20 Thread Tom Lane
I said: > "Tim Lynch" <[EMAIL PROTECTED]> writes: >> i don't see a core file. > Check that you are starting the postmaster with "ulimit -c unlimited"; > this is not the default on most Linuxen, so you may have to add that to > the start script. Also note that the postmaster never does a chdir, >

Re: [ADMIN] crash help, pgsql 7.2.1 on RH7.3

2002-11-20 Thread Tom Lane
"Tim Lynch" <[EMAIL PROTECTED]> writes: > running pgsql 7.2.1 on redhat7.3 SMP. installed a hacked glibc to fix the > mktime() timezone problem for dates < 1970 > (http://rpms.arvin.dk/glibc/rh73/i686/) > three times now the backend process has unexpectedly quit. what happens is > the postmaster p

[ADMIN] crash help, pgsql 7.2.1 on RH7.3

2002-11-20 Thread Tim Lynch
running pgsql 7.2.1 on redhat7.3 SMP. installed a hacked glibc to fix the mktime() timezone problem for dates < 1970 (http://rpms.arvin.dk/glibc/rh73/i686/) three times now the backend process has unexpectedly quit. what happens is the postmaster process and the stats processes disappear and only

Re: [ADMIN] Crash

2001-03-14 Thread Tom Lane
"John W Cunningham" <[EMAIL PROTECTED]> writes: > I ran the test - can anyone tell me what these results mean and how I can > fix it? The diffs look like locale issues --- specifically, I'd say that your server is running in en_US or some other locale with ISO-like sorting rules for strings. I a

RE: [ADMIN] Crash

2001-03-14 Thread John W Cunningham
I ran the test - can anyone tell me what these results mean and how I can fix it? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Tom Lane Sent: Wednesday, March 14, 2001 12:02 PM To: John W Cunningham Cc: [EMAIL PROTECTED] Subject: Re: [ADMIN] Crash

RE: [ADMIN] Crash

2001-03-14 Thread John W Cunningham
t: Re: [ADMIN] Crash "John W Cunningham" <[EMAIL PROTECTED]> writes: > How do I run the regression tests? See http://www.postgresql.org/users-lounge/docs/7.0/postgres/regress.htm regards, tom lane ---(end of broadcast)-

Re: [ADMIN] Crash

2001-03-14 Thread Tom Lane
"John W Cunningham" <[EMAIL PROTECTED]> writes: > How do I run the regression tests? See http://www.postgresql.org/users-lounge/docs/7.0/postgres/regress.htm regards, tom lane ---(end of broadcast)--- TIP 3: if posting/read

RE: [ADMIN] Crash

2001-03-14 Thread John W Cunningham
t: Re: [ADMIN] Crash "John W Cunningham" <[EMAIL PROTECTED]> writes: > psql: ERROR: cannot find attribute 1 of relation pg_proc_oid_index This sounds like there's something pretty fundamentally broken. Did you build your executables yourself (if so, with what compiler a

Re: [ADMIN] Crash

2001-03-14 Thread Tom Lane
"John W Cunningham" <[EMAIL PROTECTED]> writes: > psql: ERROR: cannot find attribute 1 of relation pg_proc_oid_index This sounds like there's something pretty fundamentally broken. Did you build your executables yourself (if so, with what compiler and what configuration options) or grab an RPM

[ADMIN] Crash

2001-03-14 Thread John W Cunningham
Hello All, I'm pretty new to Postgres, but have managed to build a substantial site on it. I built the entire thing locally on some dev servers, and then put it online. The production DB server is a superb machine (twin PIII Ghz, 2 gigs RAM) so it should be able to handle anything my dev server

Re: [ADMIN] Crash revoery

1999-06-23 Thread Holger Mitterwald
On Wed, 23 Jun 1999, Vadim Mikheev wrote: > Holger Mitterwald wrote: [..] > > The error-message is: > > ERROR: Index pg_proc_oid_index is not a btree > > > > The pg_proc_oid_index file in the data/base/ directory has the size 0 > > Bytes - which I think is not correct. > > I still can connect t

Re: [ADMIN] Crash revoery

1999-06-22 Thread Bruce Momjian
> > I guess in the file "pg_proc_oid_index" should be the index. So how can I > > recreate the index again so that it works fine again? > > Well. Try to > > create index proc_tmp on pg_proc (oid); > > Now cd to database dir and cp proc_tmp to pg_proc_oid_index and > > drop index proc_tmp; > >

Re: [ADMIN] Crash revoery

1999-06-22 Thread Vadim Mikheev
Holger Mitterwald wrote: > > Good mornin, > > Last night my computer crashed and after restart the postgresql > database claims about an error. Yes, I DO have a backup, but this lacks > about 2 days which I like to recover. > > The error-message is: > ERROR: Index pg_proc_oid_index is not a bt

[ADMIN] Crash revoery

1999-06-22 Thread Anonymous
Good mornin, Last night my computer crashed and after restart the postgresql database claims about an error. Yes, I DO have a backup, but this lacks about 2 days which I like to recover. The error-message is: ERROR: Index pg_proc_oid_index is not a btree The pg_proc_oid_index file in the data

[ADMIN] crash disk

1999-04-06 Thread bleveque
Hi, I've used postgresql 5.1. I lost server postgres but not data's directory. I try to install postgres6-4.2 but I cannot access to old data (PG_Version isn't the same). So I search on Internet and install a postgresql's version 5.1 But I cannot again access to my old da