Re: New CF app deployment - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: New CF app deployment
Date
Msg-id CABUevEz5U=5eLG66Scd3wkXrbsEN5OOYNN7n6JU8e3-mrY6H5A@mail.gmail.com
Whole thread Raw
In response to Re: New CF app deployment  (Magnus Hagander <magnus@hagander.net>)
Responses Re: New CF app deployment  (Robert Haas <robertmhaas@gmail.com>)
Re: New CF app deployment  (Marco Nenciarini <marco.nenciarini@2ndquadrant.it>)
List pgsql-hackers
On Sat, Feb 7, 2015 at 1:46 PM, Magnus Hagander <magnus@hagander.net> wrote:
On Sat, Feb 7, 2015 at 1:02 AM, Jeff Janes <jeff.janes@gmail.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.

--

pgsql-hackers by date:

Previous
From: Marko Tiikkaja
Date:
Subject: Re: Fetch zero result rows when executing a query?
Next
From: Michael Meskes
Date:
Subject: Re: ecpg array support, or lack thereof