AW: [HACKERS] pg_dump core dump, upgrading from 6.5b1 to 5/24 sna pshot

Started by ZEUGSWETTER Andreas IZ5over 26 years ago2 messages
#1ZEUGSWETTER Andreas IZ5
Andreas.Zeugswetter@telecom.at

Wow, the beta is actually for people to test out if their applications will
work on the new version 6.5. It is by no way for actual use, only for
testing.
Please use 6.4.2 until 6.5 is released.

Marc, can you name the betas something like alpha and not beta,
since beta seems to sound like something to use for productive work
to a lot of people (like everyone uses squid beta versions)

Andreas

Show quoted text

----------
Von: Ari Halberstadt[SMTP:ari@shore.net]
Gesendet: Dienstag, 25. Mai 1999 20:21
An: Postgres Hackers List
Betreff: [HACKERS] pg_dump core dump, upgrading from 6.5b1 to 5/24
snapshot

Hi,

I posted a related question yesterday to the general list, but Bruce
Momjian <maillist@candle.pha.pa.us> suggested it belongs on the hackers
list.

Using pg_dump with 6.5b1 on solaris sparc crashes with a core dump. This
means I can't keep backups and I can't upgrade my data model without being
able to export the old data.

On Bruce's suggestion I tried upgrading to a recent snapshot (in this case
the one from 5/24). When I killed the old postmaster and started the new
postmaster I got the following error in psql:

bboard=> \d
ERROR: nodeRead: Bad type 0

which sounds to me like maybe there was a change in the data format. Since
I can't use pg_dump to get my data out of 6.5b1 I'm a bit stuck now. For
now I've (quickly) gone back to using 6.5b1 and not the snapshot.

If one of the developers wants debug info on the coredump let me know what
you need (e.g., what commands to do in gdb--though I'll have to install
this or get run permissions from the sysadmin). I did a quick stack trace
in adb and it was dead in a call to fprintf, which I know does nothing to
help pinpoint the bug but it sounds like a typical way to kill a C
program.

-- Ari Halberstadt mailto:ari@shore.net <http://www.magiccookie.com/&gt;
PGP public key available at <http://www.magiccookie.com/pgpkey.txt&gt;

#2Ari Halberstadt
ari@shore.net
In reply to: ZEUGSWETTER Andreas IZ5 (#1)
Re: AW: [HACKERS] pg_dump core dump, upgrading from 6.5b1 to 5/24 sna pshot

ZEUGSWETTER Andreas IZ5 <Andreas.Zeugswetter@telecom.at> wrote:

Wow, the beta is actually for people to test out if their applications will
work on the new version 6.5. It is by no way for actual use, only for
testing.
Please use 6.4.2 until 6.5 is released.

I was running 6.4.2 but it had a terrible memory and/or table leak that
made it unuseable--one table got to 1GB the last week I used 6.4.2, with
only a few MB of real data. Vacuum was crashing, pg_dump was crashing, the
backend was dying. I had to go to 6.5b, which fortunately seems to have
fixed the exploding table problem.

Marc, can you name the betas something like alpha and not beta,
since beta seems to sound like something to use for productive work
to a lot of people (like everyone uses squid beta versions)

Beta does sound more reliable than alpha.

-- Ari Halberstadt mailto:ari@shore.net <http://www.magiccookie.com/&gt;
PGP public key available at <http://www.magiccookie.com/pgpkey.txt&gt;