> Evil it was. The haste with which beta3 appeared should've tipped you
> off that beta2 was badly broken :-(. What's puzzling us, though, is
> that this bug was in the WAL code from day one, and no one noticed it
Just for accuracy - this bug is not related to WAL anyhow.
This bug was in new fi
Frank Joerdens <[EMAIL PROTECTED]> writes:
> I managed to rescue my data via COPY
Oh, good.
> but if this is a 7.1-related error and not
> Frank-confusedness, then it looks like an evil issue indeed.
Evil it was. The haste with which beta3 appeared should've tipped you
off that beta2 was badly
> ERROR: Cannot insert a duplicate key into unique index
> pg_class_oid_index
> -- start log
> --
>
> Which makes me pause . . . are OIDs unique per database or
> per PostgreSQL installation? I think per database. Therefo
"Mikheev, Vadim" wrote:
>
> > [ . . . ]
> > > Restarting the server didn't make a difference.
> >
> > I upgraded to beta3 just now and the problem persists. I
> > didn't do an initdb obviously cuz
> > I cannot save the data via pg_dump. Beta3 will read beta2
> > data OK (I guess this means that
>
> You should probably write off your databases as toast ... update to
> beta3 and do an initdb. Sorry about that ...
And try to reproduce bug.
Sorry.
Vadim
Frank Joerdens <[EMAIL PROTECTED]> writes:
> Are questions related to 7.1 beta versions best directed to hackers or to
> general?
hackers is the proper place for discussing any unreleased version, I'd
say. Or you can file a bug report on pgsql-bugs, if that seems more
appropriate.
Frank Joerdens <[EMAIL PROTECTED]> writes:
> Then I had a look via psql at intranet and it turns out that it shows
> up as the database mpi mangled into the database intranet,
> contentwise; i.e. it doesn't only show the tables that are in intranet
> but also those that belong to mpi?
I think you
> [ . . . ]
> > Restarting the server didn't make a difference.
>
> I upgraded to beta3 just now and the problem persists. I
> didn't do an initdb obviously cuz
> I cannot save the data via pg_dump. Beta3 will read beta2
> data OK (I guess this means that
> an initdb is not required when going
Frank Joerdens wrote:
[ . . . ]
> Restarting the server didn't make a difference.
I upgraded to beta3 just now and the problem persists. I didn't do an initdb obviously
cuz
I cannot save the data via pg_dump. Beta3 will read beta2 data OK (I guess this means
that
an initdb is not required when
On Fri, Jan 12, 2001 at 06:05:09PM +0100, Frank Joerdens wrote:
[ . . . ]
> Does this make any sense to anyone?
Are questions related to 7.1 beta versions best directed to hackers or to
general?
- Frank
10 matches
Mail list logo
