Re: [HACKERS] pg_dump inconsistences

From: Vadim Mikheev <vadim(at)krs(dot)ru>
To: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
Cc: PostgreSQL Developers List <hackers(at)postgresql(dot)org>
Subject: Re: [HACKERS] pg_dump inconsistences
Date: 1999-05-26 04:55:34
Message-ID: 374B7EC6.31E82508@krs.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian wrote:
>
> > To return consistent results pg_dump should run all queries
> > in single transaction, in serializable mode. It's old problem.
> > But now when selects don't block writers we are able to do this.
> >
> > Comments/objections?
>
> If I understood what you were saying, I may object, but I don't, so go
> ahead. :-)

As far as I see each COPY table TO STDOUT is executed in
its own transaction. This may cause referential inconsistences
(pg_dump saves foreign keys, then other transaction deletes some
foreign and primary keys and commits, now pg_dump saves
primary keys and loses some of them, breaking referential
integrity).

Vadim

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 1999-05-26 04:57:41 Re: [HACKERS] pg_dump inconsistences
Previous Message Bruce Momjian 1999-05-26 04:33:35 Re: [HACKERS] pg_dump inconsistences