| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Matthew <matt(at)ctlno(dot)com> |
| Cc: | "'hackers '" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Postgre7.0.2 drop user bug |
| Date: | 2000-10-19 14:33:44 |
| Message-ID: | 8890.971966024@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Matthew <matt(at)ctlno(dot)com> writes:
>> The correct fix is CommandCounterIncrement() in the DROP USER loop,
>> so that later iterations can see the changes made by prior iterations.
> Since postgre now suppport referential integrity and cascading deletes,
> wouldn't it make more sense to use that code to manage the relationship
> between pg_user and pg_group (and probably a wealth of other system tables),
Dunno if it's worth the trouble to change. Certainly this particular
bug would still be a bug, whether the cascaded deletion is done "by hand"
or not.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2000-10-19 14:36:06 | Re: pgsql/doc (FAQ_MSWIN INSTALL_MSWIN) |
| Previous Message | Tom Lane | 2000-10-19 14:31:22 | Re: Postgre7.0.2 drop user bug |