Re: COPY BINARY broken on Linux/AXP

On Wed, 27 Jun 2001, Tom Lane wrote:

> pgsql-bugs(at)postgresql(dot)org writes:
> > On SuSE Linux for the Alpha(AXP) architecture 'COPY BINARY FROM'
> > seems not to be able to read a file that was generated by
> > 'COPY BINARY TO' before.
>
> Hmm. The regression tests do pass on other Linux/Alpha platforms.

I was checking it on our current development version.

Meanwhile, I re-checked it on SuSE Linux 7.1 AXP and here it works.

Interestingly, the results of the geometry tests differ also between
the two versions of Linux, I've tested. On SuSE Linux 7.1 the results
are the same as in geometry-solaris-precision.out while the
development version's results are identical to
geometry-alpha-precision.

I suspect that the newer versions of gcc or glibc are the source of
these problems. Let's see what our Alpha experts say about this...

> Could you look at the generated file and see if it seems correct
> or not? (The format is documented on the COPY reference page ---
> note that it is different in 7.1 than it was in prior releases.)

It looks at least similar to the example in the manpage:

# od -c results/stud_emp.data
0000000 P G B C O P Y \n 377 \r \n \0 004 003 002 001
0000020 \0 \0 \0 \0 \0 \0 \0 \0 \a \0 377 377 \b \0 \0 \0
0000040 j e f f 004 \0 027 \0 \0 \0 020 \0 \0 \0 \0 \0
0000060 \0 \0 @ 315 314 314 314 314 314 036 @ 004 \0 X 002
0000100 \0 \0 \0 s h a r o n \0 \0 \0 \0 \0 \0
0000120 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0
0000140 \0 \0 \0 \0 \b \0 \0 \0 \0 \0 \0 \0 \f @ \0 \0
0000160 \a \0 377 377 \a \0 \0 \0 c i m 004 \0 036 \0 \0
0000200 \0 020 \0 \0 \0 \0 \0 \0 \0 % @ 315 314 314 314 314
0000220 314 022 @ 004 \0 220 001 \0 \0 \0 \0 \b \0 3 3 3
0000240 3 3 3 \v @ \0 \0 \a \0 377 377 \t \0 \0 \0 l
0000260 i n d a 004 \0 023 \0 \0 \0 020 \0 315 314 314 314
0000300 314 314 354 ? f f f f f f 030 @ 004 \0 d \0
0000320 \0 \0 \0 \0 \b \0 3 3 3 3 3 3 \a @ \0 \0
0000340 377 377
0000342

cu
Reinhard