Martin Simmons wrote:
>> On Wed, 19 Sep 2007 18:58:13 +0200, Marc Cousin said:
>> On Wednesday 19 September 2007 16:59:10 Martin Simmons wrote:
On Wed, 19 Sep 2007 11:54:37 +0200, Cousin Marc said:
I think the problem is linked to the fact dbcheck works more or less row
by ro
> On Wed, 19 Sep 2007 18:58:13 +0200, Marc Cousin said:
>
> On Wednesday 19 September 2007 16:59:10 Martin Simmons wrote:
> > > On Wed, 19 Sep 2007 11:54:37 +0200, Cousin Marc said:
> > >
> > > I think the problem is linked to the fact dbcheck works more or less row
> > > by row.
> > >
> >
> On Wed, 19 Sep 2007 17:52:40 +0200, Cedric Devillers said:
>
> Martin Simmons wrote:
> >> On Wed, 19 Sep 2007 11:54:37 +0200, Cousin Marc said:
> >> I think the problem is linked to the fact dbcheck works more or less row
> >> by
> >> row.
> >>
> >> If I understand correctly, the probl
On Wednesday 19 September 2007 16:59:10 Martin Simmons wrote:
> > On Wed, 19 Sep 2007 11:54:37 +0200, Cousin Marc said:
> >
> > I think the problem is linked to the fact dbcheck works more or less row
> > by row.
> >
> > If I understand correctly, the problem is that you have duplicates in the
On Wednesday 19 September 2007 17:52:40 Cedric Devillers wrote:
> Martin Simmons wrote:
> >> On Wed, 19 Sep 2007 11:54:37 +0200, Cousin Marc said:
> >>
> >> I think the problem is linked to the fact dbcheck works more or less row
> >> by row.
> >>
> >> If I understand correctly, the problem is
Martin Simmons wrote:
>> On Wed, 19 Sep 2007 11:54:37 +0200, Cousin Marc said:
>> I think the problem is linked to the fact dbcheck works more or less row by
>> row.
>>
>> If I understand correctly, the problem is that you have duplicates in the
>> path
>> table as the error comes from
>> S
> On Wed, 19 Sep 2007 11:54:37 +0200, Cousin Marc said:
>
> I think the problem is linked to the fact dbcheck works more or less row by
> row.
>
> If I understand correctly, the problem is that you have duplicates in the
> path
> table as the error comes from
> SELECT PathId FROM Path WHE
I think the problem is linked to the fact dbcheck works more or less row by
row.
If I understand correctly, the problem is that you have duplicates in the path
table as the error comes from
SELECT PathId FROM Path WHERE Path='%s' returning more than one row
You could try this query, it would p
Hello,
I must run dbcheck on my bacula database (postgresql backend) because of
"sql_create.c:767 More than one Path!" warning on every file backed up
(don't know where it comes from, actually).
The operation is extremely slow, it ran for the all week-end and only
deleted 2000 from the 51000 dup
