Re: [Postgres-xc-developers] Assertion failure in REL1_1_STABLE branch

[Ashutosh B. <ash...@en...>]

This line is deleted in PG. While merging it was not deleted in XC during
manula conflict resolution.


On Sun, Jun 2, 2013 at 6:16 AM, Koichi Suzuki <koi...@gm...>wrote:

> Removed line is vanilla PG code part.   If we close twice, isn't it better
> to remove the code in XC part, if it is?
>
> At least, we should maintain #if... directive as
>
> #ifdef PGXC
>
> ...
> #else
>    relation_close(...)
> #endif
>
> ----------
> Koichi Suzuki
>
>
> 2013/5/31 Ashutosh Bapat <ash...@en...>
>
>> Hi All,
>> If we execute following set of commands in the sequence, we get an
>> assertion failure on datanode/s and an "Unexpected EOF" error message on
>> the coordinator.
>>
>> drop schema alter1, alter2 cascade;
>> create schema alter1;
>> create schema alter2;
>> create table alter1.t1(val int);
>> alter table alter1.t1 set schema alter2;
>>
>> The reason is we are closing a relation twice, once in
>> AlterTableNamespaceInternal and second time in AlterTableNamespace. The
>> first call is only in XC and not in PG. Looks like some merge error.
>>
>> Here's patch to fix this.
>>
>> --
>> Best Wishes,
>> Ashutosh Bapat
>> EntepriseDB Corporation
>> The Postgres Database Company
>>
>>
>> ------------------------------------------------------------------------------
>> Get 100% visibility into Java/.NET code with AppDynamics Lite
>> It's a free troubleshooting tool designed for production
>> Get down to code-level detail for bottlenecks, with <2% overhead.
>> Download for free and get started troubleshooting in minutes.
>> http://p.sf.net/sfu/appdyn_d2d_ap2
>> _______________________________________________
>> Postgres-xc-developers mailing list
>> Pos...@li...
>> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>>
>>
>


-- 
Best Wishes,
Ashutosh Bapat
EntepriseDB Corporation
The Postgres Database Company