On Friday 14 February 2003 17:55, Tom Lane wrote:
> Andreas Schmitz <[EMAIL PROTECTED]> writes:
> > I have a problem with the "vacuum full". every time I run the vacuum
> > command I loose data from the parent tables. maybe also from the
> > subtables (haven't checked yet). I tried it a few times u
> > > I have a problem with the "vacuum full". every time I run the vacuum
> > > command I loose data from the parent tables. maybe also from the
> > > subtables (haven't checked yet). I tried it a few times up to now an I
> > > can reproduce the phenomena.
> >
> > That sounds ugly ... but are you
Andreas Schmitz <[EMAIL PROTECTED]> writes:
> however, what kind of details do you need to
> qualify if it's a postgres problem or not ?
Ultimately, we need a way to reproduce the problem for debugging.
If it is a Postgres bug, it should be possible to reproduce it.
regar
daniel alvarez <[EMAIL PROTECTED]> writes:
> NOTICE: Rel pg_class: Uninitialized page 3344 - fixing
> NOTICE: Rel pg_class: Uninitialized page 3345 - fixing
> NOTICE: Rel pg_class: Uninitialized page 3346 - fixing
> NOTICE: Rel pg_class: Uninitialized page 3347 - fixing
> NOTICE: Rel pg_class:
I've had PostgreSQL 7.1.3 running (Mac OS X) for a while. I recently upgraded to MAC
OS X 10.2 (and it appeared that my 7.1.3 install of PostgreSQL no longer works). So
I've been trying to upgrade to 7.3. The installation package ran fine. However, when
I ran the initdb command, it failed.
[EMAIL PROTECTED] writes:
> So I've been trying to upgrade to 7.3.
> The installation package ran fine. However, when I ran the initdb
> command, it failed.
It looks like the package you are using expects libcrypto version 0.9,
and you have either no libcrypto or a different version installed.
I
