| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Pilsl <pilsl(at)goldfisch(dot)at> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: blobs dont rollback ? |
| Date: | 2000-10-23 14:17:03 |
| Message-ID: | 8189.972310623@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Peter Pilsl <pilsl(at)goldfisch(dot)at> writes:
> A table contains many entries and each entry includes a single
> blob-oid. In a databaseprocessing perlscript I need to delete such a
> blob and perform the lo_unlink and later I rollback the session without
> commiting (and even no autocommiting) in between. In my opinion this
> should have left the original blob unchanged.
Sorry, you lose: in current releases a blob is a table, and table
deletion is not rollback-able (the physical Unix file is deleted
immediately...)
This will be fixed in 7.1.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gilles DAROLD | 2000-10-23 14:19:23 | Re: Out of memory errors with mod_perl |
| Previous Message | Tom Lane | 2000-10-23 14:01:50 | Re: Updating pg_attribute - Permission denied |