Re: [Proposal] Global temporary tables
Magnus Hagander <magnus@hagander.net>
From: Magnus Hagander <magnus@hagander.net>
To: Julien Rouhaud <rjuju123@gmail.com>
Cc: 曾文旌 <wenjing.zwj@alibaba-inc.com>, Pavel Stehule <pavel.stehule@gmail.com>, Robert Haas <robertmhaas@gmail.com>, Konstantin Knizhnik <k.knizhnik@postgrespro.ru>, "movead.li@highgo.ca" <movead.li@highgo.ca>, Prabhat Sahu <prabhat.sahu@enterprisedb.com>, tushar <tushar.ahuja@enterprisedb.com>, Tomas Vondra <tomas.vondra@2ndquadrant.com>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2020-11-26T10:44:21Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
PageAddItemExtended(): Add LP_UNUSED assertion.
- 30aaab26e521 14.0 cited
-
Remove temporary files after backend crash
- cd91de0d1795 14.0 cited
-
Fix comment in indexing.c
- 9fd2952cf492 14.0 cited
-
Fix failure to ignore leftover temp tables after a server crash.
- 6919b7e32947 9.3.0 cited
On Thu, Nov 26, 2020 at 11:16 AM Julien Rouhaud <rjuju123@gmail.com> wrote: > > On Thu, Nov 26, 2020 at 4:05 PM 曾文旌 <wenjing.zwj@alibaba-inc.com> wrote: > > > > I found that the new Patch mail failed to register to Commitfest > > https://commitfest.postgresql.org/28/2349/# > > I don't know what's wrong and how to check it? > > Could you help me figure it out? > > Apparently the attachment in > https://www.postgresql.org/message-id/A3F1EBD9-E694-4384-8049-37B09308491B@alibaba-inc.com > wasn't detected. I have no idea why, maybe Magnus will know. > Otherwise you could try to ask on -www. Not offhand. The email appeas to have a fairly complex nested mime structure, so something in the python library that parses the MIME decides that it's not there. For some reason the email is 7 parts. 1 is the signature, the rest seems complexly nested. And the attachment seems to be squeezed in between two different HTML parts. Basically, at the top it's multipart/alternative, which says there are two choices. One is text/plain, which is what the archives uses. The other is a combination of text/html followed by application/octetstream (the patch) followed by another text/html. The archives picks the first alternative, which is text/plain, which does not contain the attachment. The attachment only exists in the HTML view. I think the easiest solution is to re-send as plain text email with the attachment, which would then put the attachment on the email itself instead of embedded in the HTML, I would guess. -- Magnus Hagander Me: https://www.hagander.net/ Work: https://www.redpill-linpro.com/