From cjwhite@cisco.com Tue Jan 27 01:12:19 2004 X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id D162BD1D27C for ; Tue, 27 Jan 2004 01:12:19 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 16492-01 for ; Mon, 26 Jan 2004 21:11:50 -0400 (AST) Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by svr1.postgresql.org (Postfix) with ESMTP id 6E66ED1E16B for ; Mon, 26 Jan 2004 21:11:46 -0400 (AST) Received: from sj-core-4.cisco.com (171.68.223.138) by sj-iport-5.cisco.com with ESMTP; 26 Jan 2004 17:13:59 -0800 Received: from cjwhitew2k02 (dhcp-128-107-151-36.cisco.com [128.107.151.36]) by sj-core-4.cisco.com (8.12.6/8.12.6) with ESMTP id i0R1Bj5k021711 for ; Mon, 26 Jan 2004 17:11:46 -0800 (PST) Reply-To: From: "Chris White (cjwhite)" To: Subject: Error seen when vacuuming pg_largeobject table Date: Mon, 26 Jan 2004 17:11:45 -0800 Message-ID: <002001c3e472$88698fd0$24976b80@amer.cisco.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0021_01C3E42F.7A464FD0" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4024 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4927.1200 X-Virus-Scanned: by amavisd-new at postgresql.org X-Spam-Status: No, hits=1.5 tagged_above=0.0 required=5.0 tests=HTML_20_30 X-Spam-Level: * X-Archive-Number: 200401/246 X-Sequence-Number: 12109 This is a multi-part message in MIME format. ------=_NextPart_000_0021_01C3E42F.7A464FD0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Following a power fail restart, when I vacuum the pg_largeobject table I see the following error messages: VACUUM: DEBUG sql sql sql DEBUG: --Relation pg_largeobject-- blocks 450 VACUUM: DEBUG sql sql sql DEBUG: Pages 450: Changed 78, reaped 277, Empty 0, New 37; Tup 1390: Vac 232, Keep/VTL 0/0, UnUsed 220, MinLen 98, MaxLen 2092; Re-using: Free/Avail. Space 1464136/1463348; EndEmpty/Avail. Pages 0/445. VACUUM: CPU 0.05s/0.01u sec elapsed 0.56 sec. VACUUM: DEBUG sql sql sql DEBUG: Index pg_largeobject_loid_pn_index: Pages 14; Tuples 1044: Deleted 232. VACUUM: CPU 0.00s/0.00u sec elapsed 0.00 sec. VACUUM: INFO sql sql sql NOTICE: Index pg_largeobject_loid_pn_index: NUMBER OF INDEX' TUPLES (1044) IS NOT THE SAME AS HEAP' (1390). VACUUM: Recreate the index. VACUUM: WARNING sql sql sql ERROR: Cannot insert a duplicate key into unique index pg_largeobject_loid_pn_index When I run postgres with the -P and -O options to reindex the index, everything seem to run okay, I see no error messages. However, when I restart postmaster and try and do a vacuum again, I get the same error messages. What can I do to correct the problem? Thanks Chris White ------=_NextPart_000_0021_01C3E42F.7A464FD0 Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Message
Following= a power=20 fail restart, when I vacuum the pg_largeobject table I see the following er= ror=20 messages:
 

VACUUM: DEBUG sql sql sql DEBUG: --Relation= =20 pg_largeobject-- blocks 450

VACUUM: DEBUG sql sql sql DEBUG: Pages 450: = Changed=20 78, reaped 277, Empty 0, New 37; Tup 1390: Vac 232, Keep/VTL 0/0, UnUsed 22= 0,=20 MinLen 98, MaxLen 2092; Re-using: Free/Avail. Space 1464136/1463348;=20 EndEmpty/Avail. Pages 0/445.

VACUUM: CPU 0.05s/0.01u sec elapsed 0.56=20 sec.

VACUUM: DEBUG sql sql sql DEBUG: Index=20 pg_largeobject_loid_pn_index: Pages 14; Tuples 1044: Deleted 232.

VACUUM: CPU 0.00s/0.00u sec elapsed 0.00=20 sec. VACUUM: INFO sql sql sql NOTICE: Index pg_largeobject_loid_pn_ind= ex:=20 NUMBER OF INDEX' TUPLES (1044) IS NOT THE SAME AS HEAP' (1390).

VACUUM: Recreate the index.

VACUUM: WARNING sql sql sql ERROR: Cannot in= sert a=20 duplicate key into unique index pg_largeobject_loid_pn_index

When I run = postgres=20 with the -P and -O options to reindex the index, everything seem to run oka= y, I=20 see no error messages. However, when I restart postmaster and try and do a= =20 vacuum again, I get the same error messages.

What can I = do to=20 correct the problem?

Thanks

Chris=20 White

------=_NextPart_000_0021_01C3E42F.7A464FD0-- From tgl@sss.pgh.pa.us Tue Jan 27 01:24:16 2004 X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 19F5AD1D321 for ; Tue, 27 Jan 2004 01:24:16 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 17962-08 for ; Mon, 26 Jan 2004 21:23:48 -0400 (AST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id 0BF0ED1D27C for ; Mon, 26 Jan 2004 21:23:45 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.10/8.12.10) with ESMTP id i0R1NdnX007742; Mon, 26 Jan 2004 20:23:39 -0500 (EST) To: cjwhite@cisco.com Cc: pgsql-admin@postgresql.org Subject: Re: Error seen when vacuuming pg_largeobject table In-reply-to: <002001c3e472$88698fd0$24976b80@amer.cisco.com> References: <002001c3e472$88698fd0$24976b80@amer.cisco.com> Comments: In-reply-to "Chris White (cjwhite)" message dated "Mon, 26 Jan 2004 17:11:45 -0800" Date: Mon, 26 Jan 2004 20:23:39 -0500 Message-ID: <7741.1075166619@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200401/247 X-Sequence-Number: 12110 "Chris White (cjwhite)" writes: > VACUUM: DEBUG sql sql sql DEBUG: Index pg_largeobject_loid_pn_index: > Pages 14; Tuples 1044: Deleted 232. > ... > VACUUM: WARNING sql sql sql ERROR: Cannot insert a duplicate key into > unique index pg_largeobject_loid_pn_index > When I run postgres with the -P and -O options to reindex the index, > everything seem to run okay, I see no error messages. However, when I > restart postmaster and try and do a vacuum again, I get the same error > messages. I don't think you can have reindexed the index. With only 1044 rows in it, it shouldn't take up more than 3 or 4 pages when freshly created; certainly not 14. Are you sure you reindexed in the right database? If you're sure it's not pilot error, let's see the exact transcript of what you did with the standalone postgres, and also the exact transcript (no "sql sql sql") of the failing VACUUM afterwards. Also, what PG version is this? regards, tom lane From cjwhite@cisco.com Tue Jan 27 02:00:03 2004 X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 914CCD1E0FD for ; Tue, 27 Jan 2004 02:00:03 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 30481-04 for ; Mon, 26 Jan 2004 21:59:34 -0400 (AST) Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by svr1.postgresql.org (Postfix) with ESMTP id 62876D1E1D3 for ; Mon, 26 Jan 2004 21:54:40 -0400 (AST) Received: from sj-core-4.cisco.com (171.68.223.138) by sj-iport-5.cisco.com with ESMTP; 26 Jan 2004 17:56:56 -0800 Received: from cjwhitew2k02 (dhcp-128-107-151-36.cisco.com [128.107.151.36]) by sj-core-4.cisco.com (8.12.6/8.12.6) with ESMTP id i0R1sc5k018480; Mon, 26 Jan 2004 17:54:39 -0800 (PST) Reply-To: From: "Chris White (cjwhite)" To: "'Tom Lane'" Cc: Subject: Re: Error seen when vacuuming pg_largeobject table Date: Mon, 26 Jan 2004 17:54:38 -0800 Message-ID: <003501c3e478$87e4c0b0$24976b80@amer.cisco.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4024 In-Reply-To: <7741.1075166619@sss.pgh.pa.us> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4927.1200 X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200401/248 X-Sequence-Number: 12111 Here is the info. I am running 7.2.1. bash-2.05b$ ./postgres -P -O -D /t/data/sql aesop POSTGRES backend interactive interface $Revision: 1.245.2.2 $ $Date: 2002/02/27 23:17:01 $ backend> reindex index pg_largeobject_loid_pn_index; backend> bash-2.05b$ ./psql -d aesop -U chris Welcome to psql, the PostgreSQL interactive terminal. Type: \copyright for distribution terms \h for help with SQL commands \? for help on internal slash commands \g or terminate with semicolon to execute query \q to quit aesop=# vacuum full; NOTICE: Index pg_largeobject_loid_pn_index: NUMBER OF INDEX' TUPLES (0) IS NOT THE SAME AS HEAP' (1390). Recreate the index. ERROR: Cannot insert a duplicate key into unique index pg_largeobject_loid_pn_index aesop=# \q It is slightly different in that the number of tuples in the index is (0) compared with (1044) before. Tried again, this time I tried to reindex the pg_largeobject table first. This caused even problems: bash-2.05b$ ./postgres -D /t/data/sql -P -O aesop POSTGRES backend interactive interface $Revision: 1.245.2.2 $ $Date: 2002/02/27 23:17:01 $ backend> reindex table pg_largeobject; backend> reindex index pg_largeobject_loid_pn_index; backend> bash-2.05b$ ./psql -d aesop -U voicemail Welcome to psql, the PostgreSQL interactive terminal. Type: \copyright for distribution terms \h for help with SQL commands \? for help on internal slash commands \g or terminate with semicolon to execute query \q to quit aesop=# vacuum full; NOTICE: RelationBuildDesc: can't open pg_largeobject_loid_pn_index: No such file or directory ERROR: _mdfd_getrelnfd: cannot open relation pg_largeobject_loid_pn_index: No such file or directory aesop=# \q -----Original Message----- From: Tom Lane [mailto:tgl@sss.pgh.pa.us] Sent: Monday, January 26, 2004 5:24 PM To: cjwhite@cisco.com Cc: pgsql-admin@postgresql.org Subject: Re: [ADMIN] Error seen when vacuuming pg_largeobject table "Chris White (cjwhite)" writes: > VACUUM: DEBUG sql sql sql DEBUG: Index pg_largeobject_loid_pn_index: > Pages 14; Tuples 1044: Deleted 232. ... > VACUUM: WARNING sql sql sql ERROR: Cannot insert a duplicate key into > unique index pg_largeobject_loid_pn_index > When I run postgres with the -P and -O options to reindex the index, > everything seem to run okay, I see no error messages. However, when I > restart postmaster and try and do a vacuum again, I get the same error > messages. I don't think you can have reindexed the index. With only 1044 rows in it, it shouldn't take up more than 3 or 4 pages when freshly created; certainly not 14. Are you sure you reindexed in the right database? If you're sure it's not pilot error, let's see the exact transcript of what you did with the standalone postgres, and also the exact transcript (no "sql sql sql") of the failing VACUUM afterwards. Also, what PG version is this? regards, tom lane From tgl@sss.pgh.pa.us Tue Jan 27 21:24:21 2004 X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 42100D1CCDB for ; Tue, 27 Jan 2004 21:24:21 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 71640-05 for ; Tue, 27 Jan 2004 17:23:50 -0400 (AST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id 396B8D1E256 for ; Tue, 27 Jan 2004 17:15:54 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.10/8.12.10) with ESMTP id i0RLFdnX028345; Tue, 27 Jan 2004 16:15:39 -0500 (EST) To: cjwhite@cisco.com Cc: pgsql-admin@postgresql.org Subject: Re: Error seen when vacuuming pg_largeobject table In-reply-to: <003501c3e478$87e4c0b0$24976b80@amer.cisco.com> References: <003501c3e478$87e4c0b0$24976b80@amer.cisco.com> Comments: In-reply-to "Chris White \(cjwhite\)" message dated "Mon, 26 Jan 2004 17:54:38 -0800" Date: Tue, 27 Jan 2004 16:15:39 -0500 Message-ID: <28344.1075238139@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200401/254 X-Sequence-Number: 12117 "Chris White \(cjwhite\)" writes: > Here is the info. I am running 7.2.1. 7.2.1 is a bit long in the tooth; you really ought to be running 7.2.4 if you are still in the 7.2 series. However I don't think that has much to do with your immediate problem. The only thing that struck me about your transcript is that you didn't show shutting down and restarting the postmaster. You didn't try to run a standalone backend concurrently with the postmaster did you? (There are supposed to be interlocks against that, but maybe they failed.) The failures sort of look like the standalone backend's changes did not completely propagate back to the regular database, and that's the only very plausible mechanism I can think of for that ... Also, I really wanted to see the output of vacuum verbose. Just "vacuum" doesn't tell anything much. regards, tom lane From cjwhite@cisco.com Tue Jan 27 21:48:53 2004 X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 7A81BD1B55F for ; Tue, 27 Jan 2004 21:48:53 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 80710-10 for ; Tue, 27 Jan 2004 17:48:23 -0400 (AST) Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by svr1.postgresql.org (Postfix) with ESMTP id 1E566D1E1CF for ; Tue, 27 Jan 2004 17:41:46 -0400 (AST) Received: from sj-core-4.cisco.com (171.68.223.138) by sj-iport-5.cisco.com with ESMTP; 27 Jan 2004 13:44:09 -0800 Received: from cjwhitew2k02 (dhcp-128-107-151-36.cisco.com [128.107.151.36]) by sj-core-4.cisco.com (8.12.6/8.12.6) with ESMTP id i0RLfj5k008925; Tue, 27 Jan 2004 13:41:45 -0800 (PST) Reply-To: From: "Chris White (cjwhite)" To: "'Tom Lane'" Cc: Subject: Re: Error seen when vacuuming pg_largeobject table Date: Tue, 27 Jan 2004 13:41:45 -0800 Message-ID: <004601c3e51e$5c750ba0$0b00a8c0@amer.cisco.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4024 In-Reply-To: <28344.1075238139@sss.pgh.pa.us> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4927.1200 X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200401/255 X-Sequence-Number: 12118 Cut and pasted from my screen to the e-mail. I did shutdown postmaster prior to running postgres standalone. I assume that quit from postgres backend stops it. I did restart postmaster prior running the psql vacuum full. Sorry, forgot to run verbose mode on the commands. I have re-initialized the DB and restored from a backup. Will send info if it happens again. Thanks for the help Chris -----Original Message----- From: Tom Lane [mailto:tgl@sss.pgh.pa.us] Sent: Tuesday, January 27, 2004 1:16 PM To: cjwhite@cisco.com Cc: pgsql-admin@postgresql.org Subject: Re: [ADMIN] Error seen when vacuuming pg_largeobject table "Chris White \(cjwhite\)" writes: > Here is the info. I am running 7.2.1. 7.2.1 is a bit long in the tooth; you really ought to be running 7.2.4 if you are still in the 7.2 series. However I don't think that has much to do with your immediate problem. The only thing that struck me about your transcript is that you didn't show shutting down and restarting the postmaster. You didn't try to run a standalone backend concurrently with the postmaster did you? (There are supposed to be interlocks against that, but maybe they failed.) The failures sort of look like the standalone backend's changes did not completely propagate back to the regular database, and that's the only very plausible mechanism I can think of for that ... Also, I really wanted to see the output of vacuum verbose. Just "vacuum" doesn't tell anything much. regards, tom lane From cjwhite@cisco.com Wed Jan 28 19:49:01 2004 X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id F422AD1B456 for ; Wed, 28 Jan 2004 19:49:01 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 63752-07 for ; Wed, 28 Jan 2004 15:48:32 -0400 (AST) Received: from ind-iport-1.cisco.com (ind-iport-1-sec.cisco.com [64.104.129.9]) by svr1.postgresql.org (Postfix) with ESMTP id 1CF77D1BCA7 for ; Wed, 28 Jan 2004 15:48:29 -0400 (AST) Received: from india-core-1.cisco.com (64.104.129.221) by ind-iport-1.cisco.com with ESMTP; 29 Jan 2004 06:50:07 +0530 Received: from cjwhitew2k02 (dhcp-128-107-151-87.cisco.com [128.107.151.87]) by india-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id i0SJmILo014032; Wed, 28 Jan 2004 11:48:20 -0800 (PST) Reply-To: From: "Chris White (cjwhite)" To: "'Tom Lane'" Cc: Subject: Re: Error seen when vacuuming pg_largeobject table Date: Wed, 28 Jan 2004 11:48:20 -0800 Message-ID: <000b01c3e5d7$b1224b90$57976b80@amer.cisco.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4024 In-Reply-To: <28344.1075238139@sss.pgh.pa.us> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Importance: Normal X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200401/256 X-Sequence-Number: 12119 Tom, Got it to happen again after a power fail. Here is the logs this time with verbose. bash-2.05b$ ./postgres -D /t/data/sql -P -O aesop POSTGRES backend interactive interface $Revision: 1.245.2.2 $ $Date: 2002/02/27 23:17:01 $ backend> reindex index pg_largeobject_loid_pn_index; backend> bash-2.05b$ ./postmaster -D /t/data/sql -i & [1] 324 bash-2.05b$ ./psql -d aesop -U chris Welcome to psql, the PostgreSQL interactive terminal. Type: \copyright for distribution terms \h for help with SQL commands \? for help on internal slash commands \g or terminate with semicolon to execute query \q to quit aesop=# vacuum full verbose; NOTICE: --Relation pg_type-- blocks 3 NOTICE: Pages 3: Changed 1, reaped 1, Empty 0, New 0; Tup 154: Vac 0, Keep/VTL 0/0, UnUsed 17, MinLen 106, MaxLen 106; Re-using: Free/Avail. Space 7200/7200; EndEmpty/Avail. Pages 0/3. CPU 0.00s/0.00u sec elapsed 0.00 sec. NOTICE: Index pg_type_oid_index: Pages 2; Tuples 154: Deleted 0. CPU 0.00s/0.00u sec elapsed 0.00 sec. NOTICE: Index pg_type_typname_index: Pages 2; Tuples 154: Deleted 0. CPU 0.00s/0.00u sec elapsed 0.48 sec. NOTICE: Rel pg_type: Pages: 3 --> 3; Tuple(s) moved: 0. CPU 0.00s/0.00u sec elapsed 0.00 sec. NOTICE: --Relation pg_attribute-- blocks 16 NOTICE: Pages 16: Changed 5, reaped 4, Empty 0, New 0; Tup 947: Vac 97, Keep/VTL 0/0, UnUsed 156, MinLen 98, MaxLen 98; Re-using: Free/Avail. Space 31252/6760; EndEmpty/Avail. Pages 3/1. CPU 0.00s/0.00u sec elapsed 0.00 sec. NOTICE: Index pg_attribute_relid_attnam_index: Pages 16; Tuples 947: Deleted 0. CPU 0.00s/0.00u sec elapsed 0.03 sec. NOTICE: Index pg_attribute_relid_attnum_index: Pages 7; Tuples 947: Deleted 0. CPU 0.00s/0.00u sec elapsed 0.00 sec. NOTICE: Rel pg_attribute: Pages: 16 --> 13; Tuple(s) moved: 0. CPU 0.00s/0.00u sec elapsed 0.00 sec. NOTICE: --Relation pg_class-- blocks 6 NOTICE: Pages 6: Changed 3, reaped 5, Empty 0, New 0; Tup 122: Vac 19, Keep/VTL 0/0, UnUsed 145, MinLen 116, MaxLen 152; Re-using: Free/Avail. Space 33476/1292; EndEmpty/Avail. Pages 4/1. CPU 0.00s/0.00u sec elapsed 0.00 sec. NOTICE: Index pg_class_oid_index: Pages 2; Tuples 122: Deleted 0. CPU 0.00s/0.00u sec elapsed 0.00 sec. NOTICE: Index pg_class_relname_index: Pages 4; Tuples 122: Deleted 0. CPU 0.00s/0.00u sec elapsed 0.00 sec. NOTICE: Rel pg_class: Pages: 6 --> 2; Tuple(s) moved: 0. CPU 0.00s/0.00u sec elapsed 0.00 sec. NOTICE: --Relation pg_group-- blocks 0 NOTICE: Pages 0: Changed 0, reaped 0, Empty 0, New 0; Tup 0: Vac 0, Keep/VTL 0/0, UnUsed 0, MinLen 0, MaxLen 0; Re-using: Free/Avail. Space 0/0; EndEmpty/Avail. Pages 0/0. CPU 0.00s/0.00u sec elapsed 0.00 sec. NOTICE: Index pg_group_name_index: Pages 1; Tuples 0. CPU 0.00s/0.00u sec elapsed 0.00 sec. NOTICE: Index pg_group_sysid_index: Pages 1; Tuples 0. CPU 0.00s/0.00u sec elapsed 0.00 sec. NOTICE: --Relation pg_database-- blocks 1 NOTICE: Pages 1: Changed 0, reaped 1, Empty 0, New 0; Tup 3: Vac 0, Keep/VTL 0/0, UnUsed 2, MinLen 92, MaxLen 92; Re-using: Free/Avail. Space 7876/7876; EndEmpty/Avail. Pages 0/1. CPU 0.00s/0.00u sec elapsed 0.00 sec. NOTICE: Index pg_database_datname_index: Pages 2; Tuples 3: Deleted 0. CPU 0.00s/0.00u sec elapsed 0.00 sec. NOTICE: Index pg_database_oid_index: Pages 2; Tuples 3: Deleted 0. CPU 0.00s/0.00u sec elapsed 0.00 sec. NOTICE: Rel pg_database: Pages: 1 --> 1; Tuple(s) moved: 0. CPU 0.00s/0.00u sec elapsed 0.00 sec. NOTICE: --Relation pg_inherits-- blocks 0 NOTICE: Pages 0: Changed 0, reaped 0, Empty 0, New 0; Tup 0: Vac 0, Keep/VTL 0/0, UnUsed 0, MinLen 0, MaxLen 0; Re-using: Free/Avail. Space 0/0; EndEmpty/Avail. Pages 0/0. CPU 0.00s/0.00u sec elapsed 0.00 sec. NOTICE: Index pg_inherits_relid_seqno_index: Pages 1; Tuples 0. CPU 0.00s/0.00u sec elapsed 0.01 sec. NOTICE: --Relation pg_index-- blocks 2 NOTICE: Pages 2: Changed 1, reaped 1, Empty 0, New 0; Tup 57: Vac 0, Keep/VTL 0/0, UnUsed 16, MinLen 160, MaxLen 160; Re-using: Free/Avail. Space 6932/6796; EndEmpty/Avail. Pages 0/1. CPU 0.00s/0.00u sec elapsed 0.00 sec. NOTICE: Index pg_index_indrelid_index: Pages 2; Tuples 57: Deleted 0. CPU 0.00s/0.00u sec elapsed 0.00 sec. NOTICE: Index pg_index_indexrelid_index: Pages 2; Tuples 57: Deleted 0. CPU 0.00s/0.00u sec elapsed 0.00 sec. NOTICE: Rel pg_index: Pages: 2 --> 2; Tuple(s) moved: 0. CPU 0.00s/0.00u sec elapsed 0.00 sec. NOTICE: --Relation pg_operator-- blocks 10 NOTICE: Pages 10: Changed 0, reaped 0, Empty 0, New 0; Tup 623: Vac 0, Keep/VTL 0/0, UnUsed 0, MinLen 116, MaxLen 116; Re-using: Free/Avail. Space 6960/6852; EndEmpty/Avail. Pages 0/1. CPU 0.00s/0.00u sec elapsed 0.00 sec. NOTICE: Index pg_operator_oid_index: Pages 4; Tuples 623. CPU 0.00s/0.00u sec elapsed 0.00 sec. NOTICE: Index pg_operator_oprname_l_r_k_index: Pages 8; Tuples 623. CPU 0.00s/0.00u sec elapsed 0.00 sec. NOTICE: Rel pg_operator: Pages: 10 --> 10; Tuple(s) moved: 0. CPU 0.00s/0.00u sec elapsed 0.00 sec. NOTICE: --Relation pg_opclass-- blocks 1 NOTICE: Pages 1: Changed 0, reaped 0, Empty 0, New 0; Tup 51: Vac 0, Keep/VTL 0/0, UnUsed 0, MinLen 80, MaxLen 80; Re-using: Free/Avail. Space 3888/3888; EndEmpty/Avail. Pages 0/1. CPU 0.01s/0.00u sec elapsed 0.00 sec. NOTICE: Index pg_opclass_am_name_index: Pages 2; Tuples 51. CPU 0.00s/0.00u sec elapsed 0.00 sec. NOTICE: Index pg_opclass_oid_index: Pages 2; Tuples 51. CPU 0.00s/0.00u sec elapsed 0.00 sec. NOTICE: Rel pg_opclass: Pages: 1 --> 1; Tuple(s) moved: 0. CPU 0.00s/0.00u sec elapsed 0.00 sec. NOTICE: --Relation pg_am-- blocks 1 NOTICE: Pages 1: Changed 0, reaped 0, Empty 0, New 0; Tup 4: Vac 0, Keep/VTL 0/0, UnUsed 0, MinLen 120, MaxLen 120; Re-using: Free/Avail. Space 7676/7676; EndEmpty/Avail. Pages 0/1. CPU 0.00s/0.00u sec elapsed 0.00 sec. NOTICE: Index pg_am_name_index: Pages 2; Tuples 4. CPU 0.00s/0.00u sec elapsed 0.00 sec. NOTICE: Index pg_am_oid_index: Pages 2; Tuples 4. CPU 0.00s/0.00u sec elapsed 0.00 sec. NOTICE: Rel pg_am: Pages: 1 --> 1; Tuple(s) moved: 0. CPU 0.00s/0.00u sec elapsed 0.00 sec. NOTICE: --Relation pg_amop-- blocks 2 NOTICE: Pages 2: Changed 0, reaped 0, Empty 0, New 0; Tup 180: Vac 0, Keep/VTL 0/0, UnUsed 0, MinLen 44, MaxLen 44; Re-using: Free/Avail. Space 7704/7692; EndEmpty/Avail. Pages 0/1. CPU 0.00s/0.00u sec elapsed 0.00 sec. NOTICE: Index pg_amop_opc_opr_index: Pages 2; Tuples 180. CPU 0.00s/0.00u sec elapsed 0.00 sec. NOTICE: Index pg_amop_opc_strategy_index: Pages 2; Tuples 180. CPU 0.00s/0.00u sec elapsed 0.00 sec. NOTICE: Rel pg_amop: Pages: 2 --> 2; Tuple(s) moved: 0. CPU 0.00s/0.00u sec elapsed 0.00 sec. NOTICE: --Relation pg_amproc-- blocks 1 NOTICE: Pages 1: Changed 0, reaped 0, Empty 0, New 0; Tup 57: Vac 0, Keep/VTL 0/0, UnUsed 0, MinLen 44, MaxLen 44; Re-using: Free/Avail. Space 5436/5436; EndEmpty/Avail. Pages 0/1. CPU 0.00s/0.00u sec elapsed 0.00 sec. NOTICE: Index pg_amproc_opc_procnum_index: Pages 2; Tuples 57. CPU 0.00s/0.00u sec elapsed 0.00 sec. NOTICE: Rel pg_amproc: Pages: 1 --> 1; Tuple(s) moved: 0. CPU 0.00s/0.00u sec elapsed 0.00 sec. NOTICE: --Relation pg_language-- blocks 1 NOTICE: Pages 1: Changed 0, reaped 0, Empty 0, New 0; Tup 3: Vac 0, Keep/VTL 0/0, UnUsed 0, MinLen 79, MaxLen 84; Re-using: Free/Avail. Space 7912/7912; EndEmpty/Avail. Pages 0/1. CPU 0.00s/0.00u sec elapsed 0.00 sec. NOTICE: Index pg_language_name_index: Pages 2; Tuples 3. CPU 0.00s/0.00u sec elapsed 0.00 sec. NOTICE: Index pg_language_oid_index: Pages 2; Tuples 3. CPU 0.00s/0.00u sec elapsed 0.00 sec. NOTICE: Rel pg_language: Pages: 1 --> 1; Tuple(s) moved: 0. CPU 0.00s/0.00u sec elapsed 0.00 sec. NOTICE: --Relation pg_largeobject-- blocks 637 NOTICE: Pages 637: Changed 0, reaped 396, Empty 0, New 8; Tup 2380: Vac 517, Keep/VTL 0/0, UnUsed 22, MinLen 70, MaxLen 2092; Re-using: Free/Avail. Space 1946640/1946008; EndEmpty/Avail. Pages 0/621. CPU 0.05s/0.01u sec elapsed 0.05 sec. NOTICE: Index pg_largeobject_loid_pn_index: Pages 1; Tuples 0: Deleted 0. CPU 0.00s/0.00u sec elapsed 0.00 sec. NOTICE: Index pg_largeobject_loid_pn_index: NUMBER OF INDEX' TUPLES (0) IS NOT THE SAME AS HEAP' (2380). Recreate the index. server closed the connection unexpectedly This probably means the server terminated abnormally before or while processing the request. The connection to the server was lost. Attempting reset: Succeeded. aesop=# aesop=# vacuum verbose pg_largeobject; NOTICE: Index pg_largeobject_loid_pn_index: Pages 1; Tuples 0: Deleted 0. CPU 0.01s/0.00u sec elapsed 0.00 sec. NOTICE: Removed 517 tuples in 376 pages. CPU 0.05s/0.12u sec elapsed 1.62 sec. NOTICE: Pages 637: Changed 0, Empty 1; Tup 2380: Vac 517, Keep 0, UnUsed 22. Total CPU 0.11s/0.12u sec elapsed 1.68 sec. VACUUM aesop=# vacuum full verbose pg_largeobject; NOTICE: Pages 637: Changed 0, reaped 396, Empty 7, New 1; Tup 2380: Vac 0, Keep/VTL 0/0, UnUsed 539, MinLen 70, MaxLen 2092; Re-using: Free/Avail. Space 1946640/1946008; EndEmpty/Avail. Pages 0/621. CPU 0.05s/0.00u sec elapsed 0.05 sec. NOTICE: Index pg_largeobject_loid_pn_index: Pages 1; Tuples 0: Deleted 0. CPU 0.00s/0.00u sec elapsed 0.00 sec. NOTICE: Index pg_largeobject_loid_pn_index: NUMBER OF INDEX' TUPLES (0) IS NOT THE SAME AS HEAP' (2380). Recreate the index. server closed the connection unexpectedly This probably means the server terminated abnormally before or while processing the request. The connection to the server was lost. Attempting reset: Failed. !# \q bash-2.05b$ pg_ctl stop -D /t/data/sql -m fast waiting for postmaster to shut down......done postmaster successfully shut down [1]+ Done ./postmaster -D /t/data/sql -i bash-2.05b$ ./postgres -D /t/data/sql -P -O aesop POSTGRES backend interactive interface $Revision: 1.245.2.2 $ $Date: 2002/02/27 23:17:01 $ backend> reindex index pg_largeobject_loid_pn_index; bash-2.05b$ ./postmaster -D /t/data/sql -i & [1] 359 bash-2.05b$ ./psql -d aesop -U chris Welcome to psql, the PostgreSQL interactive terminal. Type: \copyright for distribution terms \h for help with SQL commands \? for help on internal slash commands \g or terminate with semicolon to execute query \q to quit aesop=# vacuum full verbose pg_largeobject; NOTICE: --Relation pg_largeobject-- blocks 637 NOTICE: Pages 637: Changed 0, reaped 396, Empty 7, New 1; Tup 2380: Vac 0, Keep/VTL 0/0, UnUsed 539, MinLen 70, MaxLen 2092; Re-using: Free/Avail. Space 1946640/1946008; EndEmpty/Avail. Pages 0/621. CPU 0.05s/0.00u sec elapsed 0.05 sec. NOTICE: Index pg_largeobject_loid_pn_index: Pages 1; Tuples 0: Deleted 0. CPU 0.00s/0.00u sec elapsed 0.00 sec. NOTICE: Index pg_largeobject_loid_pn_index: NUMBER OF INDEX' TUPLES (0) IS NOT THE SAME AS HEAP' (2380). Recreate the index. server closed the connection unexpectedly This probably means the server terminated abnormally before or while processing the request. The connection to the server was lost. Attempting reset: Failed. !# \q bash-2.05b$ -----Original Message----- From: Tom Lane [mailto:tgl@sss.pgh.pa.us] Sent: Tuesday, January 27, 2004 1:16 PM To: cjwhite@cisco.com Cc: pgsql-admin@postgresql.org Subject: Re: [ADMIN] Error seen when vacuuming pg_largeobject table "Chris White \(cjwhite\)" writes: > Here is the info. I am running 7.2.1. 7.2.1 is a bit long in the tooth; you really ought to be running 7.2.4 if you are still in the 7.2 series. However I don't think that has much to do with your immediate problem. The only thing that struck me about your transcript is that you didn't show shutting down and restarting the postmaster. You didn't try to run a standalone backend concurrently with the postmaster did you? (There are supposed to be interlocks against that, but maybe they failed.) The failures sort of look like the standalone backend's changes did not completely propagate back to the regular database, and that's the only very plausible mechanism I can think of for that ... Also, I really wanted to see the output of vacuum verbose. Just "vacuum" doesn't tell anything much. regards, tom lane From tgl@sss.pgh.pa.us Wed Jan 28 19:52:49 2004 X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 8E2E6D1C97F for ; Wed, 28 Jan 2004 19:52:49 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 67349-07 for ; Wed, 28 Jan 2004 15:52:19 -0400 (AST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id 6D6EDD1C9DF for ; Wed, 28 Jan 2004 15:52:17 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i0SJqFBk028649; Wed, 28 Jan 2004 14:52:15 -0500 (EST) To: cjwhite@cisco.com Cc: pgsql-admin@postgresql.org Subject: Re: Error seen when vacuuming pg_largeobject table In-reply-to: <000b01c3e5d7$b1224b90$57976b80@amer.cisco.com> References: <000b01c3e5d7$b1224b90$57976b80@amer.cisco.com> Comments: In-reply-to "Chris White \(cjwhite\)" message dated "Wed, 28 Jan 2004 11:48:20 -0800" Date: Wed, 28 Jan 2004 14:52:15 -0500 Message-ID: <28648.1075319535@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200401/257 X-Sequence-Number: 12120 > Got it to happen again after a power fail. Here is the logs this time > with verbose. Hm, those backend crashes should have left core dumps; can you get a stack trace from the core? regards, tom lane From cjwhite@cisco.com Wed Jan 28 21:48:58 2004 X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 273DFD1CCB0 for ; Wed, 28 Jan 2004 21:48:58 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 18251-02 for ; Wed, 28 Jan 2004 17:48:29 -0400 (AST) Received: from ind-iport-1.cisco.com (ind-iport-1-sec.cisco.com [64.104.129.9]) by svr1.postgresql.org (Postfix) with ESMTP id 4AE82D1B474 for ; Wed, 28 Jan 2004 17:48:26 -0400 (AST) Received: from india-core-1.cisco.com (64.104.129.221) by ind-iport-1.cisco.com with ESMTP; 29 Jan 2004 08:48:38 +0530 Received: from cjwhitew2k02 (dhcp-128-107-151-87.cisco.com [128.107.151.87]) by india-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id i0SLmILo023073; Wed, 28 Jan 2004 13:48:19 -0800 (PST) Reply-To: From: "Chris White (cjwhite)" To: "'Tom Lane'" Cc: Subject: Re: Error seen when vacuuming pg_largeobject table Date: Wed, 28 Jan 2004 13:48:20 -0800 Message-ID: <001501c3e5e8$73c835a0$57976b80@amer.cisco.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4024 In-Reply-To: <28648.1075319535@sss.pgh.pa.us> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Importance: Normal X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200401/260 X-Sequence-Number: 12123 Sorry no core files. The system is running with cores turned off. Next time I will turn on cores prior to trying to debug this. Chris -----Original Message----- From: pgsql-admin-owner@postgresql.org [mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Tom Lane Sent: Wednesday, January 28, 2004 11:52 AM To: cjwhite@cisco.com Cc: pgsql-admin@postgresql.org Subject: Re: [ADMIN] Error seen when vacuuming pg_largeobject table > Got it to happen again after a power fail. Here is the logs this time > with verbose. Hm, those backend crashes should have left core dumps; can you get a stack trace from the core? regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html From mendola@bigfoot.com Wed Jan 28 22:18:01 2004 X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id B3176D1CCB9 for ; Wed, 28 Jan 2004 22:18:01 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 30200-03 for ; Wed, 28 Jan 2004 18:17:29 -0400 (AST) Received: from pns.mm.eutelsat.org (pns.mm.eutelsat.org [194.214.173.227]) by svr1.postgresql.org (Postfix) with ESMTP id D3878D1B43F for ; Wed, 28 Jan 2004 18:17:21 -0400 (AST) Received: from nts-03.mm.eutelsat.org (localhost [127.0.0.1]) by pns.mm.eutelsat.org (8.11.6/linuxconf) with ESMTP id i0SMKo922669 for ; Wed, 28 Jan 2004 23:20:50 +0100 Received: from bigfoot.com (accesspoint.mm.eutelsat.org [194.214.173.4]) by nts-03.mm.eutelsat.org (8.11.6/linuxconf) with ESMTP id i0SM2FR02335 for ; Wed, 28 Jan 2004 23:02:15 +0100 Message-ID: <4018346E.3080301@bigfoot.com> Date: Wed, 28 Jan 2004 23:15:10 +0100 From: Gaetano Mendola User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6b) Gecko/20031206 Thunderbird/0.4 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "pgsql-admin@postgresql.org" Subject: Re: Error seen when vacuuming pg_largeobject table References: <28648.1075319535@sss.pgh.pa.us> <001501c3e5e8$73c835a0$57976b80@amer.cisco.com> <40183059.2080906@bigfoot.com> <40183423.8010407@mbigroup.it> In-Reply-To: <40183423.8010407@mbigroup.it> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200401/261 X-Sequence-Number: 12124 Chris White (cjwhite) wrote: > Sorry no core files. The system is running with cores turned off. Next > time I will turn on cores prior to trying to debug this. This is not the first time that a usefull core go wasted. Happen to me twice till I realized to modify the script /etc/init.d/postgres in order to have te core file. May be is a good idea ship this file with the core file "on" ? Regards Gaetano Mendola From cjwhite@cisco.com Thu Jan 29 06:55:08 2004 X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id EB64BD1B4D1 for ; Thu, 29 Jan 2004 06:55:08 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 80636-03 for ; Thu, 29 Jan 2004 02:54:43 -0400 (AST) Received: from ind-iport-1.cisco.com (ind-iport-1-sec.cisco.com [64.104.129.9]) by svr1.postgresql.org (Postfix) with ESMTP id 481F0D1B85F for ; Thu, 29 Jan 2004 02:54:36 -0400 (AST) Received: from india-core-1.cisco.com (64.104.129.221) by ind-iport-1.cisco.com with ESMTP; 29 Jan 2004 17:54:57 +0530 Received: from cjwhitew2k02 (sjc-vpn1-1031.cisco.com [10.21.100.7]) by india-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id i0T6sWus024219; Wed, 28 Jan 2004 22:54:34 -0800 (PST) Reply-To: From: "Chris White (cjwhite)" To: "'Tom Lane'" Cc: Subject: Re: Error seen when vacuuming pg_largeobject table Date: Wed, 28 Jan 2004 22:54:34 -0800 Message-ID: <003901c3e634$c321dc90$57976b80@amer.cisco.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4024 In-Reply-To: <28648.1075319535@sss.pgh.pa.us> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Importance: Normal X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200401/263 X-Sequence-Number: 12126 Tom, It happened again. After doing the reindex, I did a vacuum full on the pg_largeobject table. This time I did not get the TUPLE INDEX error but the server terminated at the end of the vacuum command. The backend is still running even though I get the error message: aesop=# vacuum full verbose pg_largeobject; NOTICE: --Relation pg_largeobject-- blocks 21 NOTICE: Pages 21: Changed 0, reaped 19, Empty 0, New 0; Tup 69: Vac 749, Keep/VTL 0/0, UnUsed 181, MinLen 16, MaxLen 2092; Re-using: Free/Avail. Space 146752/146752; EndEmpty/Avail. Pages 0/21. CPU 0.00s/0.00u sec elapsed 0.00 sec. NOTICE: Index pg_largeobject_loid_pn_index: Pages 2; Tuples 69: Deleted 0. CPU 0.00s/0.00u sec elapsed 0.00 sec. server closed the connection unexpectedly This probably means the server terminated abnormally before or while processing the request. The connection to the server was lost. Attempting reset: Failed. It consistently happens when I try to vacuum full the pg_largeobject table. Is there anything I can get from the system to determine what is happening? Chris -----Original Message----- From: pgsql-admin-owner@postgresql.org [mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Tom Lane Sent: Wednesday, January 28, 2004 11:52 AM To: cjwhite@cisco.com Cc: pgsql-admin@postgresql.org Subject: Re: [ADMIN] Error seen when vacuuming pg_largeobject table > Got it to happen again after a power fail. Here is the logs this time > with verbose. Hm, those backend crashes should have left core dumps; can you get a stack trace from the core? regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html From tgl@sss.pgh.pa.us Thu Jan 29 15:11:00 2004 X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 99F44D1D2AC for ; Thu, 29 Jan 2004 15:11:00 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 68205-01 for ; Thu, 29 Jan 2004 11:10:38 -0400 (AST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id 7A53CD1CACD for ; Thu, 29 Jan 2004 11:10:12 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i0TFA34f022232; Thu, 29 Jan 2004 10:10:03 -0500 (EST) To: cjwhite@cisco.com Cc: pgsql-admin@postgresql.org Subject: Re: Error seen when vacuuming pg_largeobject table In-reply-to: <003901c3e634$c321dc90$57976b80@amer.cisco.com> References: <003901c3e634$c321dc90$57976b80@amer.cisco.com> Comments: In-reply-to "Chris White \(cjwhite\)" message dated "Wed, 28 Jan 2004 22:54:34 -0800" Date: Thu, 29 Jan 2004 10:10:03 -0500 Message-ID: <22231.1075389003@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200401/268 X-Sequence-Number: 12131 "Chris White \(cjwhite\)" writes: > It happened again. After doing the reindex, I did a vacuum full on the > pg_largeobject table. This time I did not get the TUPLE INDEX error but > the server terminated at the end of the vacuum command. Can you enable core dumps and get a stack trace? regards, tom lane From cjwhite@cisco.com Thu Jan 29 17:04:19 2004 X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id A3D67D1D1A4 for ; Thu, 29 Jan 2004 17:04:19 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 16360-03 for ; Thu, 29 Jan 2004 13:03:48 -0400 (AST) Received: from ind-iport-1.cisco.com (ind-iport-1-sec.cisco.com [64.104.129.9]) by svr1.postgresql.org (Postfix) with ESMTP id BF2AFD1D26D for ; Thu, 29 Jan 2004 13:03:46 -0400 (AST) Received: from india-core-1.cisco.com (64.104.129.221) by ind-iport-1.cisco.com with ESMTP; 30 Jan 2004 04:04:02 +0530 Received: from cjwhitew2k02 (dhcp-128-107-151-87.cisco.com [128.107.151.87]) by india-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id i0TH3Wus007778; Thu, 29 Jan 2004 09:03:34 -0800 (PST) Reply-To: From: "Chris White (cjwhite)" To: "'Tom Lane'" Cc: Subject: Re: Error seen when vacuuming pg_largeobject table Date: Thu, 29 Jan 2004 09:03:35 -0800 Message-ID: <006501c3e689$d6f00cb0$57976b80@amer.cisco.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4024 In-Reply-To: <22231.1075389003@sss.pgh.pa.us> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Importance: Normal X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200401/271 X-Sequence-Number: 12134 Sorry I meant to say the server terminated the connection as indicated by the error message but the server is still running and there is no core (This time I enabled them). Chris -----Original Message----- From: pgsql-admin-owner@postgresql.org [mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Tom Lane Sent: Thursday, January 29, 2004 7:10 AM To: cjwhite@cisco.com Cc: pgsql-admin@postgresql.org Subject: Re: [ADMIN] Error seen when vacuuming pg_largeobject table "Chris White \(cjwhite\)" writes: > It happened again. After doing the reindex, I did a vacuum full on the > pg_largeobject table. This time I did not get the TUPLE INDEX error > but the server terminated at the end of the vacuum command. Can you enable core dumps and get a stack trace? regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match From tgl@sss.pgh.pa.us Thu Jan 29 17:16:48 2004 X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 5E688D1B4A4 for ; Thu, 29 Jan 2004 17:16:48 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 21707-03 for ; Thu, 29 Jan 2004 13:16:17 -0400 (AST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id 1A432D1C954 for ; Thu, 29 Jan 2004 13:16:15 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i0THFV2S024301; Thu, 29 Jan 2004 12:15:31 -0500 (EST) To: cjwhite@cisco.com Cc: pgsql-admin@postgresql.org Subject: Re: Error seen when vacuuming pg_largeobject table In-reply-to: <006501c3e689$d6f00cb0$57976b80@amer.cisco.com> References: <006501c3e689$d6f00cb0$57976b80@amer.cisco.com> Comments: In-reply-to "Chris White \(cjwhite\)" message dated "Thu, 29 Jan 2004 09:03:35 -0800" Date: Thu, 29 Jan 2004 12:15:31 -0500 Message-ID: <24300.1075396531@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200401/273 X-Sequence-Number: 12136 "Chris White \(cjwhite\)" writes: > Sorry I meant to say the server terminated the connection as indicated > by the error message but the server is still running and there is no > core (This time I enabled them). Hard to believe there's no core. What shows up in the postmaster log when this happens? regards, tom lane From cjwhite@cisco.com Thu Jan 29 17:42:30 2004 X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 02CD1D1B466 for ; Thu, 29 Jan 2004 17:42:30 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 33138-01 for ; Thu, 29 Jan 2004 13:41:58 -0400 (AST) Received: from ind-iport-1.cisco.com (ind-iport-1-sec.cisco.com [64.104.129.9]) by svr1.postgresql.org (Postfix) with ESMTP id 1AEEED1B45B for ; Thu, 29 Jan 2004 13:41:57 -0400 (AST) Received: from india-core-1.cisco.com (64.104.129.221) by ind-iport-1.cisco.com with ESMTP; 30 Jan 2004 04:42:17 +0530 Received: from cjwhitew2k02 (dhcp-128-107-151-87.cisco.com [128.107.151.87]) by india-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id i0THfmus009346; Thu, 29 Jan 2004 09:41:49 -0800 (PST) Reply-To: From: "Chris White (cjwhite)" To: "'Tom Lane'" Cc: Subject: Re: Error seen when vacuuming pg_largeobject table Date: Thu, 29 Jan 2004 09:41:50 -0800 Message-ID: <006801c3e68f$2e9b5730$57976b80@amer.cisco.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4024 In-Reply-To: <24300.1075396531@sss.pgh.pa.us> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Importance: Normal X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200401/274 X-Sequence-Number: 12137 Nothing is generated to the screen and the log file is redirected to stderr. -----Original Message----- From: Tom Lane [mailto:tgl@sss.pgh.pa.us] Sent: Thursday, January 29, 2004 9:16 AM To: cjwhite@cisco.com Cc: pgsql-admin@postgresql.org Subject: Re: [ADMIN] Error seen when vacuuming pg_largeobject table "Chris White \(cjwhite\)" writes: > Sorry I meant to say the server terminated the connection as indicated > by the error message but the server is still running and there is no > core (This time I enabled them). Hard to believe there's no core. What shows up in the postmaster log when this happens? regards, tom lane