Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f4PETmA27314 for ; Fri, 25 May 2001 10:29:48 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.3/8.11.3) with ESMTP id f4PETVR05083; Fri, 25 May 2001 10:29:31 -0400 (EDT) To: Joachim Trinkwitz cc: pgsql-sql@postgresql.org Subject: Re: Problems with pg_dump (on Debian i386) In-reply-to: <87vgmp5yfd.fsf@waffel.germanistik.uni-bonn.de> References: <87vgmp5yfd.fsf@waffel.germanistik.uni-bonn.de> Comments: In-reply-to Joachim Trinkwitz message dated "25 May 2001 15:51:50 +0200" Date: Fri, 25 May 2001 10:29:31 -0400 Message-ID: <5080.990800971@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200105/272 X-Sequence-Number: 3100 Joachim Trinkwitz writes: > since some version hops, pg_dump created dump files won't be restored > correctly anymore here. In a table I have an array which holds data in > form of "x.y" values, where x are numbers and y either numbers or > letters. An example for a field including such an array is > {"1.2"}. After pg_dumping the DB, all values are OK, but when trying > to restore it, all characters after the x-value (that is, including > the dot) has vanished. Could we see a specific example please --- preferably, enough of the dump file to reproduce the problem? Also, exactly *what* version hop are we talking about? regards, tom lane