| From: | Hannu Krosing <hannu(at)trust(dot)ee> |
|---|---|
| To: | Jan Wieck <jwieck(at)debis(dot)com> |
| Cc: | David Sauer <davids(at)iol(dot)cz>, pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: [HACKERS] weird state after aborted transaction in pgsql 6.4 |
| Date: | 1998-12-02 15:00:53 |
| Message-ID: | 36655625.2B8D80E0@trust.ee |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Jan Wieck wrote:
>
> The problem is, that the CREATE TABLE is inside the
> transaction. So the catalog updates for the new table get
> rolled back, but the file is still there. On the next CREATE
> TABLE the file creation (made with O_EXCL) fails.
>
> You can safely remove the file .../data/base/david/tbl and
> you should execute CREATE/DROP statements outside of
> transactions.
Is there any plans (in TODO) to fix this ?
Either by making the CREATE/DROP totally ignore transactions (probably
hard),
ot then update the transaction machanism to be able to delete files
created
inside the transaction.
--------------
Hannu
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 1998-12-02 15:21:03 | Re: [HACKERS] NT port |
| Previous Message | Jan Wieck | 1998-12-02 12:56:54 | Re: [HACKERS] weird state after aborted transaction in pgsql 6.4 |