| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu>, Hackers List <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: create user and transactions |
| Date: | 2000-06-17 16:54:00 |
| Message-ID: | 19124.961260840@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> I can supply a patch for the create/drop user case since there's not much
> to be lost there. But what about databases? AFAIK there are no plans on
> making their creation and removal transaction friendly at all, so we'd be
> in "NOTICE: don't do that" mode for a very long time.
Agreed, we have no plans to support rollbackable CREATE or DROP
DATABASE, so I don't have an objection to erroring out on them.
But the user & group manipulation commands need to be less picky...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2000-06-17 17:03:35 | Re: Changes to functions and triggers |
| Previous Message | Tom Lane | 2000-06-17 16:47:25 | Re: OK, OK, Hiroshi's right: use a seperately-generated filename |