Hi Heikki Lin****angas,
Thanks for your quick response.
We will look for other possible reasons as mentioned by you.
Thanks and regards,
Pushker Chaubey
Heikki Lin****angas wrote:
> Pushker Chaubey wrote:
>> We took back up of a database using the following command
>> pg_dump -a
>> Please note that when we took the back the database was available
for=20
>> use simultaneously from various clients.
>>
>> In the back up file that was generated we found some data that was=20
>> violating foreign key constraints. And there fore we were not able
to=20
>> restore database back with this back up file.
>>
>> What may be the possible reasons?
>>
>> Also please tell me, is it safe if we allow concurrent modification=20
>> of data through DMLs and the same time take the back up using pg_dump?
>
> Yes, that is safe. pg_dump takes a coherent snapshot of the database=20
> as it is when the backup starts; modifications during the backup
don't=20
> show up in the backup. But clearly something has corrupted your=20
> database either before the backup or during it.
>
> Are the rows that violate the foreign key constraint still there in=20
> the original database? When was the last time you backed up? Can you=20
> check if the foreign key violation present in the previous backup as=20
> well?
>
> What does the schema of the tables involved look like? Can you post=20
> the offending rows?
>
> (this has nothing to do with JDBC, BTW. pgsql-general mailing list=20
> would be more appropriate)
>
=0D
The information contained in this electronic message and any attachments
to=
this message are intended for the exclusive use of the addressee(s) and
ma=
y contain proprietary, confidential or privileged information. If you are
n=
ot the intended recipient, you should not disseminate, distribute or copy
t=
his e-mail. Please notify the sender immediately and destroy the original
m=
essage all copies of this message and any attachments.
WARNING: Computer viruses can be transmitted via email. The recipient
shoul=
d check this email and any attachments for the presence of viruses. The
com=
pany accepts no liability for any damage caused by any virus transmitted
by=
this email.
Please do not print this email unless it is absolutely necessary.
--=20
Sent via pgsql-jdbc mailing list (pgsql-jdbc@[EMAIL PROTECTED]
)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-jdbc
|
