From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Peter Geoghegan <pg(at)heroku(dot)com>, Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: New CF app deployment |
Date: | 2015-02-08 16:04:17 |
Message-ID: | CABUevEz5U=5eLG66Scd3wkXrbsEN5OOYNN7n6JU8e3-mrY6H5A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sat, Feb 7, 2015 at 1:46 PM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
> On Sat, Feb 7, 2015 at 1:02 AM, Jeff Janes <jeff(dot)janes(at)gmail(dot)com> wrote:
>
>>
>>>
>>> One thing that would probably *help* is if the list of attachments
>>> mentioned the names of the files that were attached to each message
>>> rather than just noting that they have some kind of attachment. If
>>> people name their attachments sensibly, then you'll be able to
>>> distinguish parallel-seqscan-v23.patch from
>>> test-case-that-breaks-parallel-seqscan.sql, and that would be nice.
>>>
>>
>> Yes, I was going to request that as well.
>>
>>
> Ok, this is easy enough. There's a field missing in an API call but it
> shouldn't be that hard - I'll add this to the short term todo.
>
>
Filenames are now shown for attachments, including a direct link to the
attachment itself. I've also run a job to populate all old threads.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Meskes | 2015-02-08 16:09:11 | Re: ecpg array support, or lack thereof |
Previous Message | Marko Tiikkaja | 2015-02-08 09:17:27 | Re: Fetch zero result rows when executing a query? |