Hi Andreas,
Martin Pitt [2006-07-23 18:47 +0200]:
> Any chance to reproduce the initial problem again? Once the data
> structure is wrecked, there is little hope of automatically bringing
> it into a good state again. So we have to find out what went wrong
> initially.
Do you have any further inf
Hi Andreas,
Andreas Koch [2006-07-03 14:27 +0200]:
> > Can you please describe me how you attempted the first upgrade and
> > what failed? Any recipe for reproducing this?
>
> As far as I remember I made an dist-upgrade from stable to etch and
> ended up with the problem describted. I fixed the
Hi Martin,
> This indeed looks severely wrecked. It looks like you attempted the
> upgrade three times (first it created the 'main' cluster, then
> 'legacy', then 'transition'), and all three failed at some point. Now
> 'main' and 'legacy' are bogus clusters and 'transition' actually looks
> good,
Hallo Anreas,
sorry for the delay!
Andreas Koch [2006-05-29 13:46 +0200]:
> [layout on other PC]
> Orion:/etc/postgresql/7.4# ls -l
> insgesamt 4
> drwxr-xr-x 2 root root 4096 2005-10-13 10:03 main
>
> Orion:/etc/postgresql/7.4# ls -l main/
> insgesamt 24
> lrwxrwxrwx 1 root root 46 20
Package: postgresql
Version: 7.5.19
I'm getting the following error after upgrading from stabel to testing:
Richte postgresql ein (7.5.19) ...
Configuring already existing cluster (configuration:
/etc/postgresql/7.4/transition, data: /home/postgres/data/, owner: 111:109)
Moving configuration fil
5 matches
Mail list logo
