On 31 July 2014 10:59, Amit kapila Wrote,
Thanks for the review and valuable comments.
I have fixed all the comments and attached the revised patch.
As per your suggestion I have taken the performance report also…
Test1:
Machine Configuration:
Core : 8 (Intel(R)
Thank you Haribabu. Please see my comments inlined below i.e.
On Sun, Jul 27, 2014 at 11:42 AM, Haribabu Kommi
wrote:
> On Thu, Jul 24, 2014 at 5:59 PM, Asif Naeem wrote:
> > Sorry for being late. Thank you for sharing updated patch, sgml changes
> > seems not working i.e.
> >
> >> postgres=# s
On 04/08/14 01:27, Bruce Momjian wrote:
On Sat, Aug 2, 2014 at 11:53:06PM -0700, Mike Swanson wrote:
On Fri, 2014-08-01 at 22:28 -0700, Mike Swanson wrote:
I'd also argue that the current function basing the logic from
definition #2 has limited use even when you want to use it for such.
If you
Josh Berkus wrote:
> Currently, if archive_command is failing, pg_stop_backup() will hang
> forever. The only way to figure out what's wrong with pg_stop_backup()
> is to tail the PostgreSQL logs. This is difficult for users to
> troubleshoot, and strongly resists any kind of automation.
That
> > 1. This patch introduces a new "polygon <-> point" operator. That seems
> > useful on its own, with or without this patch.
>
> Yeah, but exact-knn cant come with no one implementation. But it would
> better come in a separate patch.
I tried to split them. Separated patches are attached. I c
On Sat, Aug 2, 2014 at 11:53:06PM -0700, Mike Swanson wrote:
> On Fri, 2014-08-01 at 22:28 -0700, Mike Swanson wrote:
> > I'd also argue that the current function basing the logic from
> > definition #2 has limited use even when you want to use it for such.
> > If you want to generate text for '(d
