| From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
|---|---|
| To: | "Howard Cole" <howardnews(at)selestial(dot)com> |
| Cc: | "'PgSql General'" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Error: Could not open relation... |
| Date: | 2008-05-23 16:07:35 |
| Message-ID: | 87prrdt35k.fsf@oxford.xeocode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"Howard Cole" <howardnews(at)selestial(dot)com> writes:
> Are there likely to be serious integrety implications if Postgres failed to
> access/write to this table for whatever reason, or would the transaction be
> rolled back.
The command would get an error and the transaction rolled back. I would be
more concerned about integrity issues if you started having the same error
with something like an xlog WAL file though.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's RemoteDBA services!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Radoslaw Zielinski | 2008-05-23 16:30:19 | Re: Fwd: sql_type tinterval not supported by DBD::Pg |
| Previous Message | Ivan Zolotukhin | 2008-05-23 15:35:43 | Re: tsearch2 on-demand dictionary loading & using functions in tsearch2 |