| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: unfixed bugs with extensions |
| Date: | 2012-10-25 13:52:10 |
| Message-ID: | 26587.1351173130@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> The other one was reported by Marko Kreen in
> http://archives.postgresql.org/message-id/CACMqXCJjauc9jPa64VxskRN67bYjuYmodz-Mgy-_aoZ6ErG3Yg@mail.gmail.com
> (the thread talks about 2 bugs, but one of them is just pilot error).
> Dimitri posted patches to the real bug for the three affected branches;
> the last one (for master) was in message
> http://archives.postgresql.org/message-id/m2391yy6ub.fsf@2ndQuadrant.fr
> I eyeballed this patch and it seemed to me to fix the problem, but I am
> unfamiliar enough with this dark corner of pg_dump that I can't be sure
> that there aren't bad behaviors being introduced inadvertently.
Yeah, I think that one's on my plate.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2012-10-25 13:53:16 | Re: WIP fix proposal for bug #6123 |
| Previous Message | Tom Lane | 2012-10-25 13:45:59 | Re: autovacuum truncate exclusive lock round two |