Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id ADD34475473 for ; Fri, 26 Apr 2002 12:04:43 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id g3QG4QF26687; Fri, 26 Apr 2002 12:04:26 -0400 (EDT) To: Christoph Haller Cc: pgsql-sql@postgresql.org Subject: Re: view on system tables upgrade? In-reply-to: <200204261505.RAA18337@rodos> References: <200204261505.RAA18337@rodos> Comments: In-reply-to Christoph Haller message dated "Fri, 26 Apr 2002 17:05:27 +0700" Date: Fri, 26 Apr 2002 12:04:25 -0400 Message-ID: <26684.1019837065@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200204/325 X-Sequence-Number: 7589 Christoph Haller writes: > All columns of type timestamp have disappeared. > Can somebody please give me a hint what happened. There's a bug in the 7.2.* pg_type table, which I found just a couple days ago: _timestamp has the wrong typelem. Since your join assumes every datatype has an array type, it fails to find a join for timestamp columns. (Should probably use an outer join there, rather than assuming that.) If you need timestamp arrays I'd suggest UPDATE pg_type SET typelem = 1114 WHERE oid = 1115; Unfortunately we cannot fix this in the 7.2.* series since we have no way to fix it in the distribution short of initdb. It'll be fixed in the 7.3 release though. regards, tom lane