| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | cpacejo(at)clearskydata(dot)com, pgsql-bugs(at)postgresql(dot)org, Robert Haas <robertmhaas(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Kouhei Kaigai <kaigai(at)ak(dot)jp(dot)nec(dot)com> |
| Subject: | Re: BUG #13666: REASSIGN OWNED BY doesn't affect the relation underlying composite type |
| Date: | 2015-12-17 17:36:33 |
| Message-ID: | 10227.1450373793@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> Alvaro Herrera wrote:
>> The commit msg says backpatched to 9.1, but given lack of backpatch of
>> another bugfix (commit 59367fdf9 for bug #9923) it doesn't actually
>> apply. I'd rather backpatch that fix and then apply this one.
> So I applied it to 9.5 and master only. If there are more votes for
> back-patching both changes to earlier branches, I can do so. I think we
> should do that -- in essence, this bug lets you corrupt your catalogs by
> dropping a user that still owns objects.
I think Bruce did not backpatch 59367fdf9 for fear of
backwards-compatibility complaints, but I tend to agree that that decision
was mistaken. The argument that you can be left with essentially corrupt
catalogs seems pretty strong.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2015-12-17 18:31:53 | Re: BUG #13681: Serialization failures caused by new multixact code of 9.3 (back-patch request) |
| Previous Message | Alvaro Herrera | 2015-12-17 17:29:37 | Re: BUG #13666: REASSIGN OWNED BY doesn't affect the relation underlying composite type |