[GENERAL] db errors

2007-10-14 Thread Akash Garg
We had a crash of one of our db systems last night. After doing a fsck of he file system and getting the db backup, we're getting a lot of these messages in our logs. The DB will also occasionally crash now. Oct 12 07:40:16 postgres[30770]: [3-1] 2007-10-12 07:40:16 PDTERROR: could not access

Re: [GENERAL] DB errors

2007-10-12 Thread Akash Garg
8.2 On 10/12/07, Filip RembiaƂkowski [EMAIL PROTECTED] wrote: 2007/10/12, Akash Garg [EMAIL PROTECTED]: We had a crash of one of our db systems last night. After doing a fsck of he file system and getting the db backup, we're getting a lot of these messages in our logs. The DB

[GENERAL] DB errors

2007-10-12 Thread Akash Garg
We had a crash of one of our db systems last night. After doing a fsck of he file system and getting the db backup, we're getting a lot of these messages in our logs. The DB will also occasionally crash now. Oct 12 07:40:16 postgres[30770]: [3-1] 2007-10-12 07:40:16 PDTERROR: could not access

[GENERAL] Long running update

2005-08-11 Thread Akash Garg
Hello, I currently running an update statement that updates every row in a very large table. This query will obviously take a long time to run. My question -- is there any way to know how much time it will take once it starts? Even something that could help me approximate the speed at which it's

Re: [GENERAL] Seg fault in postgres 7.4.7?

2005-07-18 Thread Akash Garg
I looked in the data directory of postgres -- where else should I look for it? Akash On 7/6/05, Michael Fuhr [EMAIL PROTECTED] wrote: On Wed, Jul 06, 2005 at 06:55:09PM -0700, Akash Garg wrote: This is Suse Enterprise 9.0 running on a quad Opteron Newisys machine. It has 32 gb of RAM. We

[GENERAL] Error while vacuuming

2005-07-18 Thread Akash Garg
I get this error when I run a VACUUM: INFO: vacuuming pg_toast.pg_toast_100194 vacuumdb: vacuuming of database friend failed: ERROR: could not open segment 1 of relation pg_toast_100194_index (target block 1226167840): No such file or directory I'm assuming I can just delete and recreate the

Re: [GENERAL] Error while vacuuming

2005-07-18 Thread Akash Garg
Sounds good -- I will try that. Will this REINDEX lock any queries that are currently running on the database? And is there anway to find out what table this toast table is related to? Thanks, Akash On 7/18/05, Tom Lane [EMAIL PROTECTED] wrote: Akash Garg [EMAIL PROTECTED] writes: I get

[GENERAL] Seg fault in postgres 7.4.7?

2005-07-05 Thread Akash Garg
My postgres 7.4.7 installation crashed on its own today -- here is the error log: ERROR: duplicate key violates unique constraint toolbar_pkey LOG: server process (PID 22753) was terminated by signal 11 LOG: terminating any other active server processes WARNING: terminating connection because

[GENERAL] Corrupted index

2005-06-23 Thread Akash Garg
During a vacuum, I ran into this error: vacuumdb: vacuuming of database friend failed: ERROR: invalid page header in block 41661 of relation friend_pkey I've read the posts on this newsgroup and it's clear that I have to REINDEX to fix this. The bigger question is -- why did this happen in the

Re: [GENERAL] Corrupted index

2005-06-23 Thread Akash Garg
] wrote: Akash Garg [EMAIL PROTECTED] writes: During a vacuum, I ran into this error: vacuumdb: vacuuming of database friend failed: ERROR: invalid page header in block 41661 of relation friend_pkey I've read the posts on this newsgroup and it's clear that I have to REINDEX to fix

Re: [GENERAL] Corrupted index

2005-06-23 Thread Akash Garg
I used oid2name to find the index files: 168807081 168807081.1 168807081.2 168807081.3 168807081.4 Now how do I run the od command to find the block in question? Thanks, Akash On 6/23/05, Tom Lane [EMAIL PROTECTED] wrote: Akash Garg [EMAIL PROTECTED] writes: I'll try running the od

[GENERAL] error during pg_dump

2005-06-20 Thread Akash Garg
I got this error while doing a pg_dump on one of my tables -- any ideas? pg_dump: ERROR: invalid memory alloc request size 18446744073709551613 pg_dump: SQL command to dump the contents of table users failed: PQendcopy() failed. pg_dump: Error message from server: ERROR: invalid memory alloc

[GENERAL] Error during pg_dump

2005-06-20 Thread Akash Garg
I got this error while doing a pg_dump on one of my tables -- any ideas? pg_dump: ERROR: invalid memory alloc request size 18446744073709551613 pg_dump: SQL command to dump the contents of table users failed: PQendcopy() failed. pg_dump: Error message from server: ERROR: invalid memory alloc

[GENERAL] Increasing number of postgres connections

2005-05-17 Thread Akash Garg
How do you recompile postgres to allow more than 1024 connections? Thanks, Akash ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq

[GENERAL] Increasing connection limit in postgres

2005-05-16 Thread Akash Garg
How do you recompile postgres to allow more than 1024 connections? Thanks, Akash ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org