> On Thu, Jun 25, 2015 at 11:55 PM, Robert Haas wrote:
> > On Thu, Jun 25, 2015 at 6:25 PM, Kouhei Kaigai wrote:
> >> I have a serious open item reported 1.5 month ago then reminded
> >> several times has not been fixed up yet.
> >>
> >> 9a28c8860f777e439aa12e8aea7694f8010f3...@bpxm15gp.gisp.nec.
On Thu, Jun 25, 2015 at 11:55 PM, Robert Haas wrote:
> On Thu, Jun 25, 2015 at 6:25 PM, Kouhei Kaigai wrote:
>> I have a serious open item reported 1.5 month ago then reminded
>> several times has not been fixed up yet.
>>
>> 9a28c8860f777e439aa12e8aea7694f8010f3...@bpxm15gp.gisp.nec.co.jp
>>
>>
On Thu, Jun 25, 2015 at 6:25 PM, Kouhei Kaigai wrote:
> I have a serious open item reported 1.5 month ago then reminded
> several times has not been fixed up yet.
>
> 9a28c8860f777e439aa12e8aea7694f8010f3...@bpxm15gp.gisp.nec.co.jp
>
> Patch is less than 100 lines, entirely designed according to T
On 06/25/2015 05:09 PM, Peter Geoghegan wrote:
On Thu, Jun 25, 2015 at 4:30 PM, Michael Paquier
wrote:
I'm tired of having to chase down known bugs when a patch has been
around for a long time, and an actual fix is blocking on committer
availability -- sometimes I feel the need to privately t
On Thu, Jun 25, 2015 at 4:30 PM, Michael Paquier
wrote:
>> I'm tired of having to chase down known bugs when a patch has been
>> around for a long time, and an actual fix is blocking on committer
>> availability -- sometimes I feel the need to privately twist someone's
>> arm just to get something
On Fri, Jun 26, 2015 at 8:03 AM, Peter Geoghegan wrote:
> On Thu, Jun 25, 2015 at 3:25 PM, Kouhei Kaigai wrote:
>> It is nearly obvious problem, and bugfix patch already exists.
>
> My current strategy is to post these items on the "PostgreSQL 9.5 Open
> Items" page, even when the issue is totall
On Thu, Jun 25, 2015 at 3:25 PM, Kouhei Kaigai wrote:
> It is nearly obvious problem, and bugfix patch already exists.
My current strategy is to post these items on the "PostgreSQL 9.5 Open
Items" page, even when the issue is totally trivial -- maybe that
makes a small difference, even if it some
> -Original Message-
> From: pgsql-hackers-ow...@postgresql.org
> [mailto:pgsql-hackers-ow...@postgresql.org] On Behalf Of Tom Lane
> Sent: Friday, June 26, 2015 12:00 AM
> To: pgsql-hackers@postgreSQL.org
> Subject: [HACKERS] Schedule for 9.5alpha1
>
> There wa
On Thu, Jun 25, 2015 at 12:39 PM, Andres Freund wrote:
> It'd have been easier if you'd done it the way I asked. This way I have to
> look much closer...
Well, I actually prototyped your approach to that and decided against
it only after having gone to the trouble of doing so. In any case, I
thi
On June 25, 2015 9:35:27 PM GMT+02:00, Peter Geoghegan wrote:
>On Thu, Jun 25, 2015 at 8:00 AM, Tom Lane wrote:
>> If there are any open 9.5 issues you can fix before Monday, please
>do.
>
>I have 3 pending bug fixes for UPSERT, including 2 trivial ones. This
>does not include my "minor refactori
On Thu, Jun 25, 2015 at 8:00 AM, Tom Lane wrote:
> If there are any open 9.5 issues you can fix before Monday, please do.
I have 3 pending bug fixes for UPSERT, including 2 trivial ones. This
does not include my "minor refactoring" patch, which is not a bugfix.
The last of those 3 was posted on 2
There was agreement at the PGCon dev meeting that we should put out a
9.5alpha1 release as soon as possible, to encourage wider testing
(and that it should be called an "alpha", because people aren't convinced
it's up to beta quality yet). After a little back and forth, that release
has been set f
12 matches
Mail list logo
