On Fri, May 13, 2016 at 10:14 AM, Robert Haas wrote:
> On Wed, Mar 23, 2016 at 12:53 PM, Robert Haas
> wrote:
> > On Wed, Mar 23, 2016 at 5:24 AM, Rajkumar Raghuwanshi
> > wrote:
> >> Thanks Ashutosh for the patch. I have apply and retested it, now not
> getting
> >> server crash.
> >
> > Thank
Thanks for the commit. I have tested it again. Not getting server crash now.
Thanks & Regards,
Rajkumar Raghuwanshi
QMG, EnterpriseDB Corporation
On Mon, May 16, 2016 at 9:38 PM, Robert Haas wrote:
> On Fri, May 13, 2016 at 6:40 PM, Michael Paquier
> wrote:
> > On Fri, May 13, 2016 at 11:14 PM
On Fri, May 13, 2016 at 6:40 PM, Michael Paquier
wrote:
> On Fri, May 13, 2016 at 11:14 PM, Robert Haas wrote:
>> So, barring objections, I intend to apply the attached fixup patch,
>> which replaces Michael's logic with Ashutosh's logic and rewrites the
>> comments such to be much more explicit.
On Fri, May 13, 2016 at 11:14 PM, Robert Haas wrote:
> So, barring objections, I intend to apply the attached fixup patch,
> which replaces Michael's logic with Ashutosh's logic and rewrites the
> comments such to be much more explicit.
Re-oops. I didn't check what was committed to be honest. And
On Wed, Mar 23, 2016 at 12:53 PM, Robert Haas wrote:
> On Wed, Mar 23, 2016 at 5:24 AM, Rajkumar Raghuwanshi
> wrote:
>> Thanks Ashutosh for the patch. I have apply and retested it, now not getting
>> server crash.
>
> Thanks for the report and the testing. I have committed the patch.
So it's b
> > Thanks for the report and the testing. I have committed the patch.
>
>
Thanks.
> Cool, I have refreshed the wiki page for open items accordingly.
>
Thanks.
--
Best Wishes,
Ashutosh Bapat
EnterpriseDB Corporation
The Postgres Database Company
On Thu, Mar 24, 2016 at 1:53 AM, Robert Haas wrote:
> On Wed, Mar 23, 2016 at 5:24 AM, Rajkumar Raghuwanshi
> wrote:
>> Thanks Ashutosh for the patch. I have apply and retested it, now not getting
>> server crash.
>
> Thanks for the report and the testing. I have committed the patch.
Cool, I ha
On Wed, Mar 23, 2016 at 5:24 AM, Rajkumar Raghuwanshi
wrote:
> Thanks Ashutosh for the patch. I have apply and retested it, now not getting
> server crash.
Thanks for the report and the testing. I have committed the patch.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise
On Mon, Mar 21, 2016 at 11:32 PM, Ashutosh Bapat
wrote:
>> In get_useful_ecs_for_relation, it seems to me that this assertion
>> should be removed and replaces by an actual check because even if
>> right_ec and left_ec are initialized, we cannot be sure that ec_relids
>> contains the relations spe
Thanks Ashutosh for the patch. I have apply and retested it, now not
getting server crash.
Thanks & Regards,
Rajkumar Raghuwanshi
QMG, EnterpriseDB Corporation
On Mon, Mar 21, 2016 at 8:02 PM, Ashutosh Bapat <
ashutosh.ba...@enterprisedb.com> wrote:
> Thanks Michael for looking into this.
>
>
>
Thanks Michael for looking into this.
> In get_useful_ecs_for_relation, it seems to me that this assertion
> should be removed and replaces by an actual check because even if
> right_ec and left_ec are initialized, we cannot be sure that ec_relids
> contains the relations specified:
> /*
On Fri, Mar 18, 2016 at 7:22 PM, Rajkumar Raghuwanshi
wrote:
> Hi,
>
> I am testing postgres_fdw join pushdown feature for PostgreSQL 9.6 DB, and I
> observed below issue.
>
> Observation: If do a left outer join on foreign tables more than two times.
> It is causing the server crash.
>
> Added be
12 matches
Mail list logo
