postgres-xc-developers Mailing List for Postgres-XC (Page 3)

Hi Ashutosh,

Thank you for the response.

(2013/06/12 14:43), Ashutosh Bapat wrote:
 >> Hi,
 >> >
 >> > I've investigated this problem(BUG:3614369).
 >> >
 >> > I caught the cause of it, but I can not
 >> > find where to fix.
 >> >
 >> > The problem occurs when "pgxc_collect_RTE_walker" is called 
infinitely.
 >> > It seems that rtable(List of RangeTable) become cyclic List.
 >> > I'm not sure where the List is made.
 >> >
 >> >
 > I guess, we are talking about EXECUTE DIRECT statement that you have
 > mentioned earlier.

Yes, that's right.
I'm talking about EXECUTE DIRECT statement like below.
  ---
  EXECUTE DIRECT ON (data1) $$
  SELECT
  count(*)
  FROM
  (SELECT * FROM pg_locks l LEFT JOIN
  (SELECT * FROM pg_stat_activity) s ON l.database = s.datid) a
  $$
  ---

 > The function pgxc_collect_RTE_walker() is a recursive
 > function. The condition to end the recursion is if the given node is 
NULL.
 > We have to look at if that condition is met and if not why.
 >
I investigated it deeper, and I noticed that
the infinitely loop happens at the function "range_table_walker()".

Please see below trace.
===========================
Breakpoint 1, range_table_walker (rtable=0x15e7968, walker=0x612c70 
<pgxc_collect_RTE_walker>, context=0x7fffd2de31c0,
     flags=0) at nodeFuncs.c:1908
1908    in nodeFuncs.c

(gdb) p *rtable
$10 = {type = T_List, length = 5, head = 0x15e7998, tail = 0x15e9820}
(gdb) p *rtable->head
$11 = {data = {ptr_value = 0x15e79b8, int_value = 22968760, oid_value = 
22968760}, next = 0x15e8190}
(gdb) p *rtable->head->next
$12 = {data = {ptr_value = 0x15e81b0, int_value = 22970800, oid_value = 
22970800}, next = 0x15e8988}
(gdb) p *rtable->head->next->next
$13 = {data = {ptr_value = 0x15e89a8, int_value = 22972840, oid_value = 
22972840}, next = 0x15e9018}
(gdb) p *rtable->head->next->next->next
$14 = {data = {ptr_value = 0x15e9038, int_value = 22974520, oid_value = 
22974520}, next = 0x15e9820}
(gdb) p *rtable->head->next->next->next->next
$15 = {data = {ptr_value = 0x15e9840, int_value = 22976576, oid_value = 
22976576}, next = 0x15e7998}
===========================

The line which starts with "$15" has 0x15e7998 as its next data.
But it is the head pointer(see the line which starts with $10).

And in range_table_walker(), the function is called recursively.
--------
...
         if (!(flags & QTW_IGNORE_RANGE_TABLE))
         {
                 if (range_table_walker(query->rtable, walker, context, 
flags))
                         return true;
         }
...
--------

We should make rtable right or deal with "flags" properly.
But I can't find where to do it...

What do you think ?

regards,
---------
NTT Software Corporation
Tomonari Katsumata

Hi Tomonari,



On Wed, Jun 12, 2013 at 10:17 AM, Tomonari Katsumata <
kat...@po...> wrote:

> Hi,
>
> I've investigated this problem(BUG:3614369).
>
> I caught the cause of it, but I can not
> find where to fix.
>
> The problem occurs when "pgxc_collect_RTE_walker" is called infinitely.
> It seems that rtable(List of RangeTable) become cyclic List.
> I'm not sure where the List is made.
>
>
I guess, we are talking about EXECUTE DIRECT statement that you have
mentioned earlier. The function pgxc_collect_RTE_walker() is a recursive
function. The condition to end the recursion is if the given node is NULL.
We have to look at if that condition is met and if not why.


> Anybody, please give me your help ?
> If not so difficult to fix it, I want to fix soon.
>
> --------
> NTT Software Corporation
> Tomonari Katsumata
>
> (2013/06/06 13:55), Koichi Suzuki wrote:
>  > I added this to the bug tracker with the ID 3614369
>  >
>  > Regards;
>  >
>  > ----------
>  > Koichi Suzuki
>  >
>  >
>  > 2013/6/5 鈴木 幸市 <ko...@in...>
>  >
>  >> Yeah, I found that this command stuck and doing this by direct
> connection
>  >> to datanode works.
>  >>
>  >> Regards;
>  >> ---
>  >> Koichi Suzuki
>  >>
>  >>
>  >>
>  >> On 2013/06/05, at 18:12, Tomonari Katsumata <
>  >> kat...@po...> wrote:
>  >>
>  >>> Hi,
>  >>>
>  >>> The queries sent by Suzuki-san work fine,
>  >>> but my problem is still there.
>  >>> Could you try execute the query I sent before?
>  >>>
>  >>> ---
>  >>> EXECUTE DIRECT ON (data1) $$
>  >>> SELECT
>  >>> count(*)
>  >>> FROM
>  >>> (SELECT * FROM pg_locks l LEFT JOIN
>  >>> (SELECT * FROM pg_stat_activity) s ON l.database = s.datid) a
>  >>> $$
>  >>> ---
>  >>>
>  >>> I don't change this query because it work with Postgres-XC v1.0.
>  >>>
>  >>> regards,
>  >>> -------
>  >>> NTT Software Corporation
>  >>> Tomonari Katsumata
>  >>>
>  >>> (2013/06/05 16:20), Tomonari Katsumata wrote:
>  >>>> Hi, all
>  >>>>
>  >>>> thank you for many responses!
>  >>>>
>  >>>> OK, I'll try it with the current master.
>  >>>>
>  >>>> It seems that it'll work fine...
>  >>>>
>  >>>> Sorry for bothering you.
>  >>>>
>  >>>> regards,
>  >>>> --------
>  >>>> NTT Software Corporation
>  >>>> Tomonari Katsumata
>  >>>>
>  >>>>
>  >>>> (2013/06/05 13:48), 鈴木 幸市 wrote:
>  >>>>> Now snapshot warning is disabled. Michael committed this patch.
>  >>>>>
>  >>>>> I tested the query with the current master as of this noon and I got
>  >>>> (probably) correct result.
>  >>>>> Here's the result:
>  >>>>>
>  >>>>> koichi=# execute direct on (datanode1) $$
>  >>>>> select count(*) from (select * from pg_locks) l left join
>  >>>>> (select * from pg_stat_activity) s on (l.database=s.datid);
>  >>>>> $$;
>  >>>>> count
>  >>>>> -------
>  >>>>> 9
>  >>>>> (1 row)
>  >>>>>
>  >>>>> koichi=# \q
>  >>>>> …
>  >>>>>
>  >>>>> koichi=# execute direct on (datanode1) $$
>  >>>>> koichi$# select count(*) from pg_locks l left join pg_stat_activity
> s
>  >>>>> koichi$# on (l.database=s.datid);
>  >>>>> koichi$# $$;
>  >>>>> count
>  >>>>> -------
>  >>>>> 11
>  >>>>> (1 row)
>  >>>>>
>  >>>>> koichi=#
>  >>>>>
>  >>>>> Second statement is simpler version. Anyway, they seem to work find.
>  >>>>>
>  >>>>> Katsumata-san, could you try this with the latest head? It is
>  >>>> available both from sourceforge and github.
>  >>>>> Regards;
>  >>>>> ---
>  >>>>> Koichi Suzuki
>  >>>>>
>  >>>>>
>  >>>>>
>  >>>>> On 2013/06/05, at 13:39, Ashutosh Bapat
>  >>>> <ash...@en...> wrote:
>  >>>>>>
>  >>>>>>
>  >>>>>> On Wed, Jun 5, 2013 at 9:57 AM, Tomonari Katsumata
>  >>>> <kat...@po...> wrote:
>  >>>>>> Hi Suzuki-san, Ashutosh,
>  >>>>>>
>  >>>>>>> Suzuki-san
>  >>>>>> I don't make any user tables.
>  >>>>>> As the simple example I sent before, I use only system-catalogs.
>  >>>>>>
>  >>>>>>> Ashtosh
>  >>>>>> I'm developing database monitor tool and
>  >>>>>> I use "EXECUTE DIRECT" to get database statistics data from
>  >>>>>> particular coordinator/datanode.
>  >>>>>>
>  >>>>>> :) huh
>  >>>>>>
>  >>>>>> I think, monitoring tools should directly query the datanodes or
>  >>>> coordinators. You will get snapshot warning, but that can be ignored
> I
>  >>>> guess. If they start querying coordinators, there will be performance
>  >>>> drop since coordinators directly handle the clients.
>  >>>>>> Any other thoughts?
>  >>>>>> regard,
>  >>>>>>
>  >>>>>> ---------
>  >>>>>> NTT Software Corporation
>  >>>>>> Tomonari Katsumata
>  >>>>>>
>  >>>>>> (2013/06/04 13:10), Ashutosh Bapat wrote:
>  >>>>>> Hi Tomonari,
>  >>>>>>
>  >>>>>> Thanks for the bug report.
>  >>>>>>
>  >>>>>> I am curious to know, what's the purpose of using EXECUTE DIRECT?
> We
>  >>>>>> discourage using Execute Direct in the applications. It's only for
>  >>>>>> debugging purposes.
>  >>>>>>
>  >>>>>>
>  >>>>>> On Tue, Jun 4, 2013 at 7:28 AM, Koichi Suzuki
>  >>>> <koi...@gm...>wrote:
>  >>>>>> Thank you Katsumata-san for the report.
>  >>>>>>
>  >>>>>> Could you provide CREATE TABLE statement for each table involved
> with
>  >>>> some
>  >>>>>> of the data?
>  >>>>>>
>  >>>>>> I will ad this to the bug tracker after I recreate the issue.
>  >>>>>>
>  >>>>>> Best Regards;
>  >>>>>>
>  >>>>>> ----------
>  >>>>>> Koichi Suzuki
>  >>>>>>
>  >>>>>>
>  >>>>>> 2013/6/4 Tomonari Katsumata <kat...@po...>
>  >>>>>>
>  >>>>>> Hi, I have a problem with query executing.
>  >>>>>>
>  >>>>>> I cant't have any response when I execute a query.
>  >>>>>> This problem occurs when some conditions are met.
>  >>>>>>
>  >>>>>> The conditions are below.
>  >>>>>>
> ---------------------------------------------------------------------
>  >>>>>> 1. Issuing "EXECUTE DIRECT" to Datanode(ofcourse, via Coordinator).
>  >>>>>>
>  >>>>>> 2. The Query Executing on Datanode has subquery on its FROM-clause.
>  >>>>>>
>  >>>>>> 3. In the subquery, it has a JOIN clause.
>  >>>>>>
>  >>>>>> 4. The Join clause is consisted with another subquery.
>  >>>>>>
> ---------------------------------------------------------------------
>  >>>>>>
>  >>>>>>
>  >>>>>> Simple example query is below.
>  >>>>>> ---------------------------------------------------------------
>  >>>>>> EXECUTE DIRECT ON (data1) $$
>  >>>>>> SELECT
>  >>>>>> count(*)
>  >>>>>> FROM
>  >>>>>> (SELECT * FROM pg_locks l LEFT JOIN
>  >>>>>> (SELECT * FROM pg_stat_activity) s ON l.database = s.datid) a
>  >>>>>> $$
>  >>>>>> ---------------------------------------------------------------
>  >>>>>>
>  >>>>>> FYI:
>  >>>>>> This query works fine with Postgres-XC 1.0.3.
>  >>>>>> Is this already known bug ?
>  >>>>>>
>  >>>>>>
>  >>>>>> How can I avoid this problem ?
>  >>>>>> And what kind of info do you need to investigate it ?
>  >>>>>>
>  >>>>>> ----------
>  >>>>>> NTT Software Corporation
>  >>>>>> Tomonari Katsumata
>
>
>
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> 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

Hi,

I've investigated this problem(BUG:3614369).

I caught the cause of it, but I can not
find where to fix.

The problem occurs when "pgxc_collect_RTE_walker" is called infinitely.
It seems that rtable(List of RangeTable) become cyclic List.
I'm not sure where the List is made.

Anybody, please give me your help ?
If not so difficult to fix it, I want to fix soon.

--------
NTT Software Corporation
Tomonari Katsumata

(2013/06/06 13:55), Koichi Suzuki wrote:
 > I added this to the bug tracker with the ID 3614369
 >
 > Regards;
 >
 > ----------
 > Koichi Suzuki
 >
 >
 > 2013/6/5 鈴木 幸市 <ko...@in...>
 >
 >> Yeah, I found that this command stuck and doing this by direct 
connection
 >> to datanode works.
 >>
 >> Regards;
 >> ---
 >> Koichi Suzuki
 >>
 >>
 >>
 >> On 2013/06/05, at 18:12, Tomonari Katsumata <
 >> kat...@po...> wrote:
 >>
 >>> Hi,
 >>>
 >>> The queries sent by Suzuki-san work fine,
 >>> but my problem is still there.
 >>> Could you try execute the query I sent before?
 >>>
 >>> ---
 >>> EXECUTE DIRECT ON (data1) $$
 >>> SELECT
 >>> count(*)
 >>> FROM
 >>> (SELECT * FROM pg_locks l LEFT JOIN
 >>> (SELECT * FROM pg_stat_activity) s ON l.database = s.datid) a
 >>> $$
 >>> ---
 >>>
 >>> I don't change this query because it work with Postgres-XC v1.0.
 >>>
 >>> regards,
 >>> -------
 >>> NTT Software Corporation
 >>> Tomonari Katsumata
 >>>
 >>> (2013/06/05 16:20), Tomonari Katsumata wrote:
 >>>> Hi, all
 >>>>
 >>>> thank you for many responses!
 >>>>
 >>>> OK, I'll try it with the current master.
 >>>>
 >>>> It seems that it'll work fine...
 >>>>
 >>>> Sorry for bothering you.
 >>>>
 >>>> regards,
 >>>> --------
 >>>> NTT Software Corporation
 >>>> Tomonari Katsumata
 >>>>
 >>>>
 >>>> (2013/06/05 13:48), 鈴木 幸市 wrote:
 >>>>> Now snapshot warning is disabled. Michael committed this patch.
 >>>>>
 >>>>> I tested the query with the current master as of this noon and I got
 >>>> (probably) correct result.
 >>>>> Here's the result:
 >>>>>
 >>>>> koichi=# execute direct on (datanode1) $$
 >>>>> select count(*) from (select * from pg_locks) l left join
 >>>>> (select * from pg_stat_activity) s on (l.database=s.datid);
 >>>>> $$;
 >>>>> count
 >>>>> -------
 >>>>> 9
 >>>>> (1 row)
 >>>>>
 >>>>> koichi=# \q
 >>>>> …
 >>>>>
 >>>>> koichi=# execute direct on (datanode1) $$
 >>>>> koichi$# select count(*) from pg_locks l left join pg_stat_activity s
 >>>>> koichi$# on (l.database=s.datid);
 >>>>> koichi$# $$;
 >>>>> count
 >>>>> -------
 >>>>> 11
 >>>>> (1 row)
 >>>>>
 >>>>> koichi=#
 >>>>>
 >>>>> Second statement is simpler version. Anyway, they seem to work find.
 >>>>>
 >>>>> Katsumata-san, could you try this with the latest head? It is
 >>>> available both from sourceforge and github.
 >>>>> Regards;
 >>>>> ---
 >>>>> Koichi Suzuki
 >>>>>
 >>>>>
 >>>>>
 >>>>> On 2013/06/05, at 13:39, Ashutosh Bapat
 >>>> <ash...@en...> wrote:
 >>>>>>
 >>>>>>
 >>>>>> On Wed, Jun 5, 2013 at 9:57 AM, Tomonari Katsumata
 >>>> <kat...@po...> wrote:
 >>>>>> Hi Suzuki-san, Ashutosh,
 >>>>>>
 >>>>>>> Suzuki-san
 >>>>>> I don't make any user tables.
 >>>>>> As the simple example I sent before, I use only system-catalogs.
 >>>>>>
 >>>>>>> Ashtosh
 >>>>>> I'm developing database monitor tool and
 >>>>>> I use "EXECUTE DIRECT" to get database statistics data from
 >>>>>> particular coordinator/datanode.
 >>>>>>
 >>>>>> :) huh
 >>>>>>
 >>>>>> I think, monitoring tools should directly query the datanodes or
 >>>> coordinators. You will get snapshot warning, but that can be ignored I
 >>>> guess. If they start querying coordinators, there will be performance
 >>>> drop since coordinators directly handle the clients.
 >>>>>> Any other thoughts?
 >>>>>> regard,
 >>>>>>
 >>>>>> ---------
 >>>>>> NTT Software Corporation
 >>>>>> Tomonari Katsumata
 >>>>>>
 >>>>>> (2013/06/04 13:10), Ashutosh Bapat wrote:
 >>>>>> Hi Tomonari,
 >>>>>>
 >>>>>> Thanks for the bug report.
 >>>>>>
 >>>>>> I am curious to know, what's the purpose of using EXECUTE DIRECT? We
 >>>>>> discourage using Execute Direct in the applications. It's only for
 >>>>>> debugging purposes.
 >>>>>>
 >>>>>>
 >>>>>> On Tue, Jun 4, 2013 at 7:28 AM, Koichi Suzuki
 >>>> <koi...@gm...>wrote:
 >>>>>> Thank you Katsumata-san for the report.
 >>>>>>
 >>>>>> Could you provide CREATE TABLE statement for each table involved 
with
 >>>> some
 >>>>>> of the data?
 >>>>>>
 >>>>>> I will ad this to the bug tracker after I recreate the issue.
 >>>>>>
 >>>>>> Best Regards;
 >>>>>>
 >>>>>> ----------
 >>>>>> Koichi Suzuki
 >>>>>>
 >>>>>>
 >>>>>> 2013/6/4 Tomonari Katsumata <kat...@po...>
 >>>>>>
 >>>>>> Hi, I have a problem with query executing.
 >>>>>>
 >>>>>> I cant't have any response when I execute a query.
 >>>>>> This problem occurs when some conditions are met.
 >>>>>>
 >>>>>> The conditions are below.
 >>>>>> 
---------------------------------------------------------------------
 >>>>>> 1. Issuing "EXECUTE DIRECT" to Datanode(ofcourse, via Coordinator).
 >>>>>>
 >>>>>> 2. The Query Executing on Datanode has subquery on its FROM-clause.
 >>>>>>
 >>>>>> 3. In the subquery, it has a JOIN clause.
 >>>>>>
 >>>>>> 4. The Join clause is consisted with another subquery.
 >>>>>> 
---------------------------------------------------------------------
 >>>>>>
 >>>>>>
 >>>>>> Simple example query is below.
 >>>>>> ---------------------------------------------------------------
 >>>>>> EXECUTE DIRECT ON (data1) $$
 >>>>>> SELECT
 >>>>>> count(*)
 >>>>>> FROM
 >>>>>> (SELECT * FROM pg_locks l LEFT JOIN
 >>>>>> (SELECT * FROM pg_stat_activity) s ON l.database = s.datid) a
 >>>>>> $$
 >>>>>> ---------------------------------------------------------------
 >>>>>>
 >>>>>> FYI:
 >>>>>> This query works fine with Postgres-XC 1.0.3.
 >>>>>> Is this already known bug ?
 >>>>>>
 >>>>>>
 >>>>>> How can I avoid this problem ?
 >>>>>> And what kind of info do you need to investigate it ?
 >>>>>>
 >>>>>> ----------
 >>>>>> NTT Software Corporation
 >>>>>> Tomonari Katsumata

Hi,
Attached please find a WIP patch that provides the functionality of
preparing the statement at the datanodes as soon as it is prepared
on the coordinator.
This is to take care of a test case in plancache that makes sure that
change of search_path is ignored by replans.
While the patch fixes this replan test case and the regression works fine
there are still these two problems I have to take care of.

1. This test case fails

    CREATE TABLE xc_alter_table_3 (a int, b varchar(10)) DISTRIBUTE BY
HASH(a);
    INSERT INTO xc_alter_table_3 VALUES (1, 'a');
    PREPARE d3 AS DELETE FROM xc_alter_table_3 WHERE a = $1; -- fails

    test=# explain verbose DELETE FROM xc_alter_table_3 WHERE a = 1;
                       QUERY PLAN
    -------------------------------------------------------------------
     Delete on public.xc_alter_table_3  (cost=0.00..0.00 rows=1000 width=14)
       Node/s: data_node_1, data_node_2, data_node_3, data_node_4
       Remote query: DELETE FROM ONLY xc_alter_table_3 WHERE
                     ((xc_alter_table_3.ctid = $1) AND
(xc_alter_table_3.xc_node_id = $2))
       ->  Data Node Scan on xc_alter_table_3 "_REMOTE_TABLE_QUERY_"
(cost=0.00..0.00 rows=1000 width=14)
             Output: xc_alter_table_3.a, xc_alter_table_3.ctid,
xc_alter_table_3.xc_node_id
             Node/s: data_node_3
             Remote query: SELECT a, ctid, xc_node_id FROM ONLY
xc_alter_table_3 WHERE (a = 1)
    (7 rows)

   The reason of the failure is that the select query is selecting 3 items,
the first of which is an int,
   whereas the delete query is comparing $1 with a ctid.
   I am not sure how this works without prepare, but it fails when used
with prepare.

   The reason of this planning is this section of code in function
pgxc_build_dml_statement
    else if (cmdtype == CMD_DELETE)
    {
        /*
         * Since there is no data to update, the first param is going to be
         * ctid.
         */
        ctid_param_num = 1;
    }

   Amit/Ashutosh can you suggest a fix for this problem?
   There are a number of possibilities.
   a) The select should not have selected column a.
   b) The DELETE should have referred to $2 and $3 for ctid and xc_node_id
respectively.
   c) Since the query works without PREPARE, we should make PREPARE work
the same way.


2. This test case in plancache fails.

    -- Try it with a view, which isn't directly used in the resulting plan
    -- but should trigger invalidation anyway
    create table tab33 (a int, b int);
    insert into tab33 values(1,2);
    CREATE VIEW v_tab33 AS SELECT * FROM tab33;
    PREPARE vprep AS SELECT * FROM v_tab33;
    EXECUTE vprep;
    CREATE OR REPLACE VIEW v_tab33 AS SELECT a, b/2 AS q2 FROM tab33;
    -- does not cause plan invalidation because views are never created on
datanodes
    EXECUTE vprep;

   and the reason of the failure is that views are never created on the
datanodes hence plan invalidation is not triggered.
   This can be documented as an XC limitation.

3. I still have to add comments in the patch and some ifdefs may be missing
too.


In addition to the patch I have also attached some example Java programs
that test the some basic functionality through JDBC. I found that these
programs are working fine after my patch.

1. Prepared.java : Issues parameterized delete, insert and update through
JDBC. These are un-named prepared statements and works fine.
2. NamedPrepared.java : Issues two named prepared statements through JDBC
and works fine.
3. Retrieve.java : Runs a simple select to verify results.
The comments on top of the files explain their usage.

Comments are welcome.

Thanks
Regards


On Mon, Jun 3, 2013 at 10:54 AM, Ashutosh Bapat <
ash...@en...> wrote:

>
>
>
> On Mon, Jun 3, 2013 at 10:51 AM, Abbas Butt <abb...@en...>wrote:
>
>>
>>
>> On Mon, Jun 3, 2013 at 8:43 AM, Ashutosh Bapat <
>> ash...@en...> wrote:
>>
>>>
>>>
>>>
>>> On Mon, Jun 3, 2013 at 7:40 AM, Abbas Butt <abb...@en...>wrote:
>>>
>>>> Attached please find updated patch to fix the bug. The patch takes care
>>>> of the bug and the regression issues resulting from the changes done in the
>>>> patch. Please note that the issue in test case plancache still stands
>>>> unsolved because of the following test case (simplified but taken from
>>>> plancache.sql)
>>>>
>>>> create schema s1 create table abc (f1 int);
>>>> create schema s2 create table abc (f1 int);
>>>>
>>>>
>>>> insert into s1.abc values(123);
>>>> insert into s2.abc values(456);
>>>>
>>>> set search_path = s1;
>>>>
>>>> prepare p1 as select f1 from abc;
>>>> execute p1; -- works fine, results in 123
>>>>
>>>> set search_path = s2;
>>>> execute p1; -- works fine after the patch, results in 123
>>>>
>>>> alter table s1.abc add column f2 float8;   -- force replan
>>>> execute p1; -- fails
>>>>
>>>>
>>> Huh! The beast bit us.
>>>
>>> I think the right solution here is either of two
>>> 1. Take your previous patch to always use qualified names (but you need
>>> to improve it not to affect the view dumps)
>>> 2. Prepare the statements at the datanode at the time of prepare.
>>>
>>>
>>> Is this test added new in 9.2?
>>>
>>
>> No, it was added by commit 547b6e537aa8bbae83a8a4c4d0d7f216390bdb9c in
>> March 2007.
>>
>>
>>> Why didn't we see this issue the first time prepare was implemented? I
>>> don't remember (but it was two years back).
>>>
>>
>> I was unable to locate the exact reason but since statements were not
>> being prepared on datanodes due to a merge issue this issue just surfaced
>> up.
>>
>>
>
> Well, even though statements were not getting prepared (actually prepared
> statements were not being used again and again) on datanodes, we never
> prepared them on datanode at the time of preparing the statement. So, this
> bug should have shown itself long back.
>
>
>>
>>>
>>>> The last execute should result in 123, whereas it results in 456. The
>>>> reason is that the search path has already been changed at the datanode and
>>>> a replan would mean select from abc in s2.
>>>>
>>>>
>>>>
>>>>
>>>> On Tue, May 28, 2013 at 7:17 PM, Ashutosh Bapat <
>>>> ash...@en...> wrote:
>>>>
>>>>> Hi Abbas,
>>>>> I think the fix is on the right track. There are couple of
>>>>> improvements that we need to do here (but you may not do those if the time
>>>>> doesn't permit).
>>>>>
>>>>> 1. We should have a status in RemoteQuery node, as to whether the
>>>>> query in the node should use extended protocol or not, rather than relying
>>>>> on the presence of statement name and parameters etc. Amit has already
>>>>> added a status with that effect. We need to leverage it.
>>>>>
>>>>>
>>>>> On Tue, May 28, 2013 at 9:04 AM, Abbas Butt <
>>>>> abb...@en...> wrote:
>>>>>
>>>>>> The patch fixes the dead code issue, that I described earlier. The
>>>>>> code was dead because of two issues:
>>>>>>
>>>>>> 1. The function CompleteCachedPlan was wrongly setting stmt_name to
>>>>>> NULL and this was the main reason ActivateDatanodeStatementOnNode was not
>>>>>> being called in the function pgxc_start_command_on_connection.
>>>>>> 2. The function SetRemoteStatementName was wrongly assuming that a
>>>>>> prepared statement must have some parameters.
>>>>>>
>>>>>> Fixing these two issues makes sure that the function
>>>>>> ActivateDatanodeStatementOnNode is now called and statements get prepared
>>>>>> on the datanode.
>>>>>> This patch would fix bug 3607975. It would however not fix the test
>>>>>> case I described in my previous email because of reasons I described.
>>>>>>
>>>>>>
>>>>>> On Tue, May 28, 2013 at 5:50 PM, Ashutosh Bapat <
>>>>>> ash...@en...> wrote:
>>>>>>
>>>>>>> Can you please explain what this fix does? It would help to have an
>>>>>>> elaborate explanation with code snippets.
>>>>>>>
>>>>>>>
>>>>>>> On Sun, May 26, 2013 at 10:18 PM, Abbas Butt <
>>>>>>> abb...@en...> wrote:
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Fri, May 24, 2013 at 7:04 PM, Ashutosh Bapat <
>>>>>>>> ash...@en...> wrote:
>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Fri, May 24, 2013 at 9:01 AM, Abbas Butt <
>>>>>>>>> abb...@en...> wrote:
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Fri, May 24, 2013 at 7:22 AM, Ashutosh Bapat <
>>>>>>>>>> ash...@en...> wrote:
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Thu, May 23, 2013 at 9:21 PM, Abbas Butt <
>>>>>>>>>>> abb...@en...> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Hi,
>>>>>>>>>>>>
>>>>>>>>>>>> While working on test case plancache it was brought up as a
>>>>>>>>>>>> review comment that solving bug id 3607975 should solve the problem of the
>>>>>>>>>>>> test case.
>>>>>>>>>>>> However there is some confusion in the statement of bug id
>>>>>>>>>>>> 3607975.
>>>>>>>>>>>>
>>>>>>>>>>>> "When a user does and PREPARE and then EXECUTEs multiple times,
>>>>>>>>>>>> the coordinator keeps on preparing and executing the query on datanode al
>>>>>>>>>>>> times, as against preparing once and executing multiple times. This is
>>>>>>>>>>>> because somehow the remote query is being prepared as an unnamed statement."
>>>>>>>>>>>>
>>>>>>>>>>>> Consider this test case
>>>>>>>>>>>>
>>>>>>>>>>>> A. create table abc(a int, b int);
>>>>>>>>>>>> B. insert into abc values(11, 22);
>>>>>>>>>>>> C. prepare p1 as select * from abc;
>>>>>>>>>>>> D. execute p1;
>>>>>>>>>>>> E. execute p1;
>>>>>>>>>>>> F. execute p1;
>>>>>>>>>>>>
>>>>>>>>>>>> Here are the confusions
>>>>>>>>>>>>
>>>>>>>>>>>> 1. The coordinator never prepares on datanode in response to a
>>>>>>>>>>>> prepare issued by a user.
>>>>>>>>>>>>      In fact step C does nothing on the datanodes.
>>>>>>>>>>>>      Step D simply sends "SELECT a, b FROM abc" to all
>>>>>>>>>>>> datanodes.
>>>>>>>>>>>>
>>>>>>>>>>>> 2. In step D, ExecuteQuery calls BuildCachedPlan to build a new
>>>>>>>>>>>> generic plan,
>>>>>>>>>>>>     and steps E and F use the already built generic plan.
>>>>>>>>>>>>     For details see function GetCachedPlan.
>>>>>>>>>>>>     This means that executing a prepared statement again and
>>>>>>>>>>>> again does use cached plans
>>>>>>>>>>>>     and does not prepare again and again every time we issue an
>>>>>>>>>>>> execute.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>> The problem is not here. The problem is in do_query() where
>>>>>>>>>>> somehow the name of prepared statement gets wiped out and we keep on
>>>>>>>>>>> preparing unnamed statements at the datanode.
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> We never prepare any named/unnamed statements on the datanode. I
>>>>>>>>>> spent time looking at the code written in do_query and functions called
>>>>>>>>>> from with in do_query to handle prepared statements but the code written in
>>>>>>>>>> pgxc_start_command_on_connection to handle statements prepared on datanodes
>>>>>>>>>> is dead as of now. It is never called during the complete regression run.
>>>>>>>>>> The function ActivateDatanodeStatementOnNode is never called. The way
>>>>>>>>>> prepared statements are being handled now is the same as I described
>>>>>>>>>> earlier in the mail chain with the help of an example.
>>>>>>>>>> The code that is dead was originally added by Mason through
>>>>>>>>>> commit d6d2d3d925f571b0b58ff6b4f6504d88e96bb342, back in December 2010.
>>>>>>>>>> This code has been changed a lot over the last two years. This commit does
>>>>>>>>>> not contain any test cases so I am not sure how did it use to work back
>>>>>>>>>> then.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> This code wasn't dead, when I worked on prepared statements. So,
>>>>>>>>> something has gone wrong in-between. That's what we need to find out and
>>>>>>>>> fix. Not preparing statements on the datanode is not good for performance
>>>>>>>>> either.
>>>>>>>>>
>>>>>>>>
>>>>>>>> I was able to find the reason why the code was dead and the
>>>>>>>> attached patch (WIP) fixes the problem. This would now ensure that
>>>>>>>> statements are prepared on datanodes whenever required. However there is a
>>>>>>>> problem in the way prepared statements are handled. The problem is that
>>>>>>>> unless a prepared statement is executed it is never prepared on datanodes,
>>>>>>>> hence changing the path before executing the statement gives us incorrect
>>>>>>>> results. For Example
>>>>>>>>
>>>>>>>>   create schema s1 create table abc (f1 int) distribute by
>>>>>>>> replication;
>>>>>>>>   create schema s2 create table abc (f1 int) distribute by
>>>>>>>> replication;
>>>>>>>>
>>>>>>>>   insert into s1.abc values(123);
>>>>>>>>   insert into s2.abc values(456);
>>>>>>>>   set search_path = s2;
>>>>>>>>   prepare p1 as select f1 from abc;
>>>>>>>>   set search_path = s1;
>>>>>>>>   execute p1;
>>>>>>>>
>>>>>>>> The last execute results in 123, where as it should have resulted
>>>>>>>> in 456.
>>>>>>>> I can finalize the attached patch by fixing any regression issues
>>>>>>>> that may result and that would fix 3607975 and improve performance however
>>>>>>>> the above test case would still fail.
>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> My conclusion is that the bug ID 3607975 is not reproducible.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>> Did you verify it under the debugger? If that would have been
>>>>>>>>>>> the case, we would not have seen this problem if search_path changed in
>>>>>>>>>>> between steps D and E.
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> If search path is changed between steps D & E, the problem occurs
>>>>>>>>>> because when the remote query node is created, schema qualification is not
>>>>>>>>>> added in the sql statement to be sent to the datanode, but changes in
>>>>>>>>>> search path do get communicated to the datanode. The sql statement is built
>>>>>>>>>> when execute is issued for the first time and is reused on subsequent
>>>>>>>>>> executes. The datanode is totally unaware that the select that it just
>>>>>>>>>> received is due to an execute of a prepared statement that was prepared
>>>>>>>>>> when search path was some thing else.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>> Fixing the prepared statements the way I suggested, would fix the
>>>>>>>>> problem, since the statement will get prepared at the datanode, with the
>>>>>>>>> same search path settings, as it would on the coordinator.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>>  Comments are welcome.
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> *Abbas*
>>>>>>>>>>>>  Architect
>>>>>>>>>>>>
>>>>>>>>>>>> Ph: 92.334.5100153
>>>>>>>>>>>>  Skype ID: gabbasb
>>>>>>>>>>>> www.enterprisedb.co <http://www.enterprisedb.com/>m<http://www.enterprisedb.com/>
>>>>>>>>>>>> *
>>>>>>>>>>>> Follow us on Twitter*
>>>>>>>>>>>> @EnterpriseDB
>>>>>>>>>>>>
>>>>>>>>>>>> Visit EnterpriseDB for tutorials, webinars, whitepapers<http://www.enterprisedb.com/resources-community>and more<http://www.enterprisedb.com/resources-community>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> ------------------------------------------------------------------------------
>>>>>>>>>>>> Try New Relic Now & We'll Send You this Cool Shirt
>>>>>>>>>>>> New Relic is the only SaaS-based application performance
>>>>>>>>>>>> monitoring service
>>>>>>>>>>>> that delivers powerful full stack analytics. Optimize and
>>>>>>>>>>>> monitor your
>>>>>>>>>>>> browser, app, & servers with just a few lines of code. Try New
>>>>>>>>>>>> Relic
>>>>>>>>>>>> and get this awesome Nerd Life shirt!
>>>>>>>>>>>> http://p.sf.net/sfu/newrelic_d2d_may
>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>> 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
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> --
>>>>>>>>>> *Abbas*
>>>>>>>>>>  Architect
>>>>>>>>>>
>>>>>>>>>> Ph: 92.334.5100153
>>>>>>>>>>  Skype ID: gabbasb
>>>>>>>>>> www.enterprisedb.co <http://www.enterprisedb.com/>m<http://www.enterprisedb.com/>
>>>>>>>>>> *
>>>>>>>>>> Follow us on Twitter*
>>>>>>>>>> @EnterpriseDB
>>>>>>>>>>
>>>>>>>>>> Visit EnterpriseDB for tutorials, webinars, whitepapers<http://www.enterprisedb.com/resources-community>and more<http://www.enterprisedb.com/resources-community>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Best Wishes,
>>>>>>>>> Ashutosh Bapat
>>>>>>>>> EntepriseDB Corporation
>>>>>>>>> The Postgres Database Company
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> --
>>>>>>>> *Abbas*
>>>>>>>>  Architect
>>>>>>>>
>>>>>>>> Ph: 92.334.5100153
>>>>>>>>  Skype ID: gabbasb
>>>>>>>> www.enterprisedb.co <http://www.enterprisedb.com/>m<http://www.enterprisedb.com/>
>>>>>>>> *
>>>>>>>> Follow us on Twitter*
>>>>>>>> @EnterpriseDB
>>>>>>>>
>>>>>>>> Visit EnterpriseDB for tutorials, webinars, whitepapers<http://www.enterprisedb.com/resources-community>and more<http://www.enterprisedb.com/resources-community>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Best Wishes,
>>>>>>> Ashutosh Bapat
>>>>>>> EntepriseDB Corporation
>>>>>>> The Postgres Database Company
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> --
>>>>>> *Abbas*
>>>>>>  Architect
>>>>>>
>>>>>> Ph: 92.334.5100153
>>>>>>  Skype ID: gabbasb
>>>>>> www.enterprisedb.co <http://www.enterprisedb.com/>m<http://www.enterprisedb.com/>
>>>>>> *
>>>>>> Follow us on Twitter*
>>>>>> @EnterpriseDB
>>>>>>
>>>>>> Visit EnterpriseDB for tutorials, webinars, whitepapers<http://www.enterprisedb.com/resources-community>and more<http://www.enterprisedb.com/resources-community>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Best Wishes,
>>>>> Ashutosh Bapat
>>>>> EntepriseDB Corporation
>>>>> The Postgres Database Company
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> --
>>>> *Abbas*
>>>>  Architect
>>>>
>>>> Ph: 92.334.5100153
>>>>  Skype ID: gabbasb
>>>> www.enterprisedb.co <http://www.enterprisedb.com/>m<http://www.enterprisedb.com/>
>>>> *
>>>> Follow us on Twitter*
>>>> @EnterpriseDB
>>>>
>>>> Visit EnterpriseDB for tutorials, webinars, whitepapers<http://www.enterprisedb.com/resources-community>and more<http://www.enterprisedb.com/resources-community>
>>>>
>>>
>>>
>>>
>>> --
>>> Best Wishes,
>>> Ashutosh Bapat
>>> EntepriseDB Corporation
>>> The Postgres Database Company
>>>
>>
>>
>>
>> --
>> --
>> *Abbas*
>>  Architect
>>
>> Ph: 92.334.5100153
>>  Skype ID: gabbasb
>> www.enterprisedb.co <http://www.enterprisedb.com/>m<http://www.enterprisedb.com/>
>> *
>> Follow us on Twitter*
>> @EnterpriseDB
>>
>> Visit EnterpriseDB for tutorials, webinars, whitepapers<http://www.enterprisedb.com/resources-community>and more<http://www.enterprisedb.com/resources-community>
>>
>
>
>
> --
> Best Wishes,
> Ashutosh Bapat
> EntepriseDB Corporation
> The Postgres Database Company
>



-- 
-- 
*Abbas*
 Architect

Ph: 92.334.5100153
 Skype ID: gabbasb
www.enterprisedb.co
<http://www.enterprisedb.com/>m<http://www.enterprisedb.com/>
*
Follow us on Twitter*
@EnterpriseDB

Visit EnterpriseDB for tutorials, webinars,
whitepapers<http://www.enterprisedb.com/resources-community>and
more<http://www.enterprisedb.com/resources-community>

Hi Suzuki-sun

Thanks a lot.
If I notice something, I'll report again!

regards,
--------
NTT Software Corporation
Tomonari Katsumata

(2013/06/06 13:55), Koichi Suzuki wrote:
> I added this to the bug tracker with the ID 3614369
>
> Regards;
>
> ----------
> Koichi Suzuki
>
>
> 2013/6/5 鈴木 幸市 <ko...@in...>
>
>> Yeah, I found that this command stuck and doing this by direct connection
>> to datanode works.
>>
>> Regards;
>> ---
>> Koichi Suzuki
>>
>>
>>
>> On 2013/06/05, at 18:12, Tomonari Katsumata <
>> kat...@po...> wrote:
>>
>>> Hi,
>>>
>>> The queries sent by Suzuki-san work fine,
>>> but my problem is still there.
>>> Could you try execute the query I sent before?
>>>
>>> ---
>>> EXECUTE DIRECT ON (data1) $$
>>> SELECT
>>> count(*)
>>> FROM
>>> (SELECT * FROM pg_locks l LEFT JOIN
>>> (SELECT * FROM pg_stat_activity) s ON l.database = s.datid) a
>>> $$
>>> ---
>>>
>>> I don't change this query because it work with Postgres-XC v1.0.
>>>
>>> regards,
>>> -------
>>> NTT Software Corporation
>>> Tomonari Katsumata
>>>
>>> (2013/06/05 16:20), Tomonari Katsumata wrote:
>>>> Hi, all
>>>>
>>>> thank you for many responses!
>>>>
>>>> OK, I'll try it with the current master.
>>>>
>>>> It seems that it'll work fine...
>>>>
>>>> Sorry for bothering you.
>>>>
>>>> regards,
>>>> --------
>>>> NTT Software Corporation
>>>> Tomonari Katsumata
>>>>
>>>>
>>>> (2013/06/05 13:48), 鈴木 幸市 wrote:
>>>>> Now snapshot warning is disabled. Michael committed this patch.
>>>>>
>>>>> I tested the query with the current master as of this noon and I got
>>>> (probably) correct result.
>>>>> Here's the result:
>>>>>
>>>>> koichi=# execute direct on (datanode1) $$
>>>>> select count(*) from (select * from pg_locks) l left join
>>>>> (select * from pg_stat_activity) s on (l.database=s.datid);
>>>>> $$;
>>>>> count
>>>>> -------
>>>>> 9
>>>>> (1 row)
>>>>>
>>>>> koichi=# \q
>>>>> …
>>>>>
>>>>> koichi=# execute direct on (datanode1) $$
>>>>> koichi$# select count(*) from pg_locks l left join pg_stat_activity s
>>>>> koichi$# on (l.database=s.datid);
>>>>> koichi$# $$;
>>>>> count
>>>>> -------
>>>>> 11
>>>>> (1 row)
>>>>>
>>>>> koichi=#
>>>>>
>>>>> Second statement is simpler version. Anyway, they seem to work find.
>>>>>
>>>>> Katsumata-san, could you try this with the latest head? It is
>>>> available both from sourceforge and github.
>>>>> Regards;
>>>>> ---
>>>>> Koichi Suzuki
>>>>>
>>>>>
>>>>>
>>>>> On 2013/06/05, at 13:39, Ashutosh Bapat
>>>> <ash...@en...> wrote:
>>>>>>
>>>>>> On Wed, Jun 5, 2013 at 9:57 AM, Tomonari Katsumata
>>>> <kat...@po...> wrote:
>>>>>> Hi Suzuki-san, Ashutosh,
>>>>>>
>>>>>>> Suzuki-san
>>>>>> I don't make any user tables.
>>>>>> As the simple example I sent before, I use only system-catalogs.
>>>>>>
>>>>>>> Ashtosh
>>>>>> I'm developing database monitor tool and
>>>>>> I use "EXECUTE DIRECT" to get database statistics data from
>>>>>> particular coordinator/datanode.
>>>>>>
>>>>>> :) huh
>>>>>>
>>>>>> I think, monitoring tools should directly query the datanodes or
>>>> coordinators. You will get snapshot warning, but that can be ignored I
>>>> guess. If they start querying coordinators, there will be performance
>>>> drop since coordinators directly handle the clients.
>>>>>> Any other thoughts?
>>>>>> regard,
>>>>>>
>>>>>> ---------
>>>>>> NTT Software Corporation
>>>>>> Tomonari Katsumata
>>>>>>
>>>>>> (2013/06/04 13:10), Ashutosh Bapat wrote:
>>>>>> Hi Tomonari,
>>>>>>
>>>>>> Thanks for the bug report.
>>>>>>
>>>>>> I am curious to know, what's the purpose of using EXECUTE DIRECT? We
>>>>>> discourage using Execute Direct in the applications. It's only for
>>>>>> debugging purposes.
>>>>>>
>>>>>>
>>>>>> On Tue, Jun 4, 2013 at 7:28 AM, Koichi Suzuki
>>>> <koi...@gm...>wrote:
>>>>>> Thank you Katsumata-san for the report.
>>>>>>
>>>>>> Could you provide CREATE TABLE statement for each table involved with
>>>> some
>>>>>> of the data?
>>>>>>
>>>>>> I will ad this to the bug tracker after I recreate the issue.
>>>>>>
>>>>>> Best Regards;
>>>>>>
>>>>>> ----------
>>>>>> Koichi Suzuki
>>>>>>
>>>>>>
>>>>>> 2013/6/4 Tomonari Katsumata <kat...@po...>
>>>>>>
>>>>>> Hi, I have a problem with query executing.
>>>>>>
>>>>>> I cant't have any response when I execute a query.
>>>>>> This problem occurs when some conditions are met.
>>>>>>
>>>>>> The conditions are below.
>>>>>> ---------------------------------------------------------------------
>>>>>> 1. Issuing "EXECUTE DIRECT" to Datanode(ofcourse, via Coordinator).
>>>>>>
>>>>>> 2. The Query Executing on Datanode has subquery on its FROM-clause.
>>>>>>
>>>>>> 3. In the subquery, it has a JOIN clause.
>>>>>>
>>>>>> 4. The Join clause is consisted with another subquery.
>>>>>> ---------------------------------------------------------------------
>>>>>>
>>>>>>
>>>>>> Simple example query is below.
>>>>>> ---------------------------------------------------------------
>>>>>> EXECUTE DIRECT ON (data1) $$
>>>>>> SELECT
>>>>>> count(*)
>>>>>> FROM
>>>>>> (SELECT * FROM pg_locks l LEFT JOIN
>>>>>> (SELECT * FROM pg_stat_activity) s ON l.database = s.datid) a
>>>>>> $$
>>>>>> ---------------------------------------------------------------
>>>>>>
>>>>>> FYI:
>>>>>> This query works fine with Postgres-XC 1.0.3.
>>>>>> Is this already known bug ?
>>>>>>
>>>>>>
>>>>>> How can I avoid this problem ?
>>>>>> And what kind of info do you need to investigate it ?
>>>>>>
>>>>>> ----------
>>>>>> NTT Software Corporation
>>>>>> Tomonari Katsumata
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>> ------------------------------------------------------------------------------
>>>>>> How ServiceNow helps IT people transform IT departments:
>>>>>> 1. A cloud service to automate IT design, transition and operations
>>>>>> 2. Dashboards that offer high-level views of enterprise services
>>>>>> 3. A single system of record for all IT processes
>>>>>> http://p.sf.net/sfu/servicenow-d2d-j
>>>>>> _______________________________________________
>>>>>> Postgres-xc-developers mailing list
>>>>>> Pos...@li...
>>>>>> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>> ------------------------------------------------------------------------------
>>>>>> How ServiceNow helps IT people transform IT departments:
>>>>>> 1. A cloud service to automate IT design, transition and operations
>>>>>> 2. Dashboards that offer high-level views of enterprise services
>>>>>> 3. A single system of record for all IT processes
>>>>>> http://p.sf.net/sfu/servicenow-d2d-j
>>>>>> _______________________________________________
>>>>>> Postgres-xc-developers mailing list
>>>>>> Pos...@li...
>>>>>> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> --------------------------------------------
>>>>>> NTTソフトウェア株式会社
>>>>>> 技術開発センター OSS基盤技術部門
>>>>>> 勝俣 智成
>>>>>> TEL：045-212-7665
>>>>>> FAX：045-662-7856
>>>>>> E-Mail: kat...@po...
>>>>>> --------------------------------------------
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Best Wishes,
>>>>>> Ashutosh Bapat
>>>>>> EntepriseDB Corporation
>>>>>> The Postgres Database Company
>>>>>>
>> ------------------------------------------------------------------------------
>>>>>> How ServiceNow helps IT people transform IT departments:
>>>>>> 1. A cloud service to automate IT design, transition and operations
>>>>>> 2. Dashboards that offer high-level views of enterprise services
>>>>>> 3. A single system of record for all IT processes
>>>>>>
>> http://p.sf.net/sfu/servicenow-d2d-j_______________________________________________
>>>>>> Postgres-xc-developers mailing list
>>>>>> Pos...@li...
>>>>>> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>>>>
>>>>
>>>>
>> ------------------------------------------------------------------------------
>>>> How ServiceNow helps IT people transform IT departments:
>>>> 1. A cloud service to automate IT design, transition and operations
>>>> 2. Dashboards that offer high-level views of enterprise services
>>>> 3. A single system of record for all IT processes
>>>> http://p.sf.net/sfu/servicenow-d2d-j
>>>> _______________________________________________
>>>> Postgres-xc-developers mailing list
>>>> Pos...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>>>>
>>>
>>> --
>>> --------------------------------------------
>>> NTTソフトウェア株式会社
>>>   技術開発センター OSS基盤技術部門
>>>   勝俣 智成
>>> TEL：045-212-7665
>>> FAX：045-662-7856
>>> E-Mail: kat...@po...
>>> --------------------------------------------
>>>
>>>
>>>
>>>
>> ------------------------------------------------------------------------------
>>> How ServiceNow helps IT people transform IT departments:
>>> 1. A cloud service to automate IT design, transition and operations
>>> 2. Dashboards that offer high-level views of enterprise services
>>> 3. A single system of record for all IT processes
>>> http://p.sf.net/sfu/servicenow-d2d-j
>>> _______________________________________________
>>> Postgres-xc-developers mailing list
>>> Pos...@li...
>>> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>>>
>>
>>
>> ------------------------------------------------------------------------------
>> How ServiceNow helps IT people transform IT departments:
>> 1. A cloud service to automate IT design, transition and operations
>> 2. Dashboards that offer high-level views of enterprise services
>> 3. A single system of record for all IT processes
>> http://p.sf.net/sfu/servicenow-d2d-j
>> _______________________________________________
>> Postgres-xc-developers mailing list
>> Pos...@li...
>> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>>


-- 
--------------------------------------------
NTTソフトウェア株式会社
   技術開発センター OSS基盤技術部門
   勝俣 智成
TEL：045-212-7665
FAX：045-662-7856
E-Mail: kat...@po...
--------------------------------------------

I added this to the bug tracker with the ID 3614369

Regards;

----------
Koichi Suzuki


2013/6/5 鈴木 幸市 <ko...@in...>

> Yeah, I found that this command stuck and doing this by direct connection
> to datanode works.
>
> Regards;
> ---
> Koichi Suzuki
>
>
>
> On 2013/06/05, at 18:12, Tomonari Katsumata <
> kat...@po...> wrote:
>
> > Hi,
> >
> > The queries sent by Suzuki-san work fine,
> > but my problem is still there.
> > Could you try execute the query I sent before?
> >
> > ---
> > EXECUTE DIRECT ON (data1) $$
> > SELECT
> > count(*)
> > FROM
> > (SELECT * FROM pg_locks l LEFT JOIN
> > (SELECT * FROM pg_stat_activity) s ON l.database = s.datid) a
> > $$
> > ---
> >
> > I don't change this query because it work with Postgres-XC v1.0.
> >
> > regards,
> > -------
> > NTT Software Corporation
> > Tomonari Katsumata
> >
> > (2013/06/05 16:20), Tomonari Katsumata wrote:
> >> Hi, all
> >>
> >> thank you for many responses!
> >>
> >> OK, I'll try it with the current master.
> >>
> >> It seems that it'll work fine...
> >>
> >> Sorry for bothering you.
> >>
> >> regards,
> >> --------
> >> NTT Software Corporation
> >> Tomonari Katsumata
> >>
> >>
> >> (2013/06/05 13:48), 鈴木 幸市 wrote:
> >>> Now snapshot warning is disabled. Michael committed this patch.
> >>>
> >>> I tested the query with the current master as of this noon and I got
> >> (probably) correct result.
> >>> Here's the result:
> >>>
> >>> koichi=# execute direct on (datanode1) $$
> >>> select count(*) from (select * from pg_locks) l left join
> >>> (select * from pg_stat_activity) s on (l.database=s.datid);
> >>> $$;
> >>> count
> >>> -------
> >>> 9
> >>> (1 row)
> >>>
> >>> koichi=# \q
> >>> …
> >>>
> >>> koichi=# execute direct on (datanode1) $$
> >>> koichi$# select count(*) from pg_locks l left join pg_stat_activity s
> >>> koichi$# on (l.database=s.datid);
> >>> koichi$# $$;
> >>> count
> >>> -------
> >>> 11
> >>> (1 row)
> >>>
> >>> koichi=#
> >>>
> >>> Second statement is simpler version. Anyway, they seem to work find.
> >>>
> >>> Katsumata-san, could you try this with the latest head? It is
> >> available both from sourceforge and github.
> >>> Regards;
> >>> ---
> >>> Koichi Suzuki
> >>>
> >>>
> >>>
> >>> On 2013/06/05, at 13:39, Ashutosh Bapat
> >> <ash...@en...> wrote:
> >>>>
> >>>>
> >>>> On Wed, Jun 5, 2013 at 9:57 AM, Tomonari Katsumata
> >> <kat...@po...> wrote:
> >>>> Hi Suzuki-san, Ashutosh,
> >>>>
> >>>>> Suzuki-san
> >>>> I don't make any user tables.
> >>>> As the simple example I sent before, I use only system-catalogs.
> >>>>
> >>>>> Ashtosh
> >>>> I'm developing database monitor tool and
> >>>> I use "EXECUTE DIRECT" to get database statistics data from
> >>>> particular coordinator/datanode.
> >>>>
> >>>> :) huh
> >>>>
> >>>> I think, monitoring tools should directly query the datanodes or
> >> coordinators. You will get snapshot warning, but that can be ignored I
> >> guess. If they start querying coordinators, there will be performance
> >> drop since coordinators directly handle the clients.
> >>>> Any other thoughts?
> >>>> regard,
> >>>>
> >>>> ---------
> >>>> NTT Software Corporation
> >>>> Tomonari Katsumata
> >>>>
> >>>> (2013/06/04 13:10), Ashutosh Bapat wrote:
> >>>> Hi Tomonari,
> >>>>
> >>>> Thanks for the bug report.
> >>>>
> >>>> I am curious to know, what's the purpose of using EXECUTE DIRECT? We
> >>>> discourage using Execute Direct in the applications. It's only for
> >>>> debugging purposes.
> >>>>
> >>>>
> >>>> On Tue, Jun 4, 2013 at 7:28 AM, Koichi Suzuki
> >> <koi...@gm...>wrote:
> >>>> Thank you Katsumata-san for the report.
> >>>>
> >>>> Could you provide CREATE TABLE statement for each table involved with
> >> some
> >>>> of the data?
> >>>>
> >>>> I will ad this to the bug tracker after I recreate the issue.
> >>>>
> >>>> Best Regards;
> >>>>
> >>>> ----------
> >>>> Koichi Suzuki
> >>>>
> >>>>
> >>>> 2013/6/4 Tomonari Katsumata <kat...@po...>
> >>>>
> >>>> Hi, I have a problem with query executing.
> >>>>
> >>>> I cant't have any response when I execute a query.
> >>>> This problem occurs when some conditions are met.
> >>>>
> >>>> The conditions are below.
> >>>> ---------------------------------------------------------------------
> >>>> 1. Issuing "EXECUTE DIRECT" to Datanode(ofcourse, via Coordinator).
> >>>>
> >>>> 2. The Query Executing on Datanode has subquery on its FROM-clause.
> >>>>
> >>>> 3. In the subquery, it has a JOIN clause.
> >>>>
> >>>> 4. The Join clause is consisted with another subquery.
> >>>> ---------------------------------------------------------------------
> >>>>
> >>>>
> >>>> Simple example query is below.
> >>>> ---------------------------------------------------------------
> >>>> EXECUTE DIRECT ON (data1) $$
> >>>> SELECT
> >>>> count(*)
> >>>> FROM
> >>>> (SELECT * FROM pg_locks l LEFT JOIN
> >>>> (SELECT * FROM pg_stat_activity) s ON l.database = s.datid) a
> >>>> $$
> >>>> ---------------------------------------------------------------
> >>>>
> >>>> FYI:
> >>>> This query works fine with Postgres-XC 1.0.3.
> >>>> Is this already known bug ?
> >>>>
> >>>>
> >>>> How can I avoid this problem ?
> >>>> And what kind of info do you need to investigate it ?
> >>>>
> >>>> ----------
> >>>> NTT Software Corporation
> >>>> Tomonari Katsumata
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>
> ------------------------------------------------------------------------------
> >>>> How ServiceNow helps IT people transform IT departments:
> >>>> 1. A cloud service to automate IT design, transition and operations
> >>>> 2. Dashboards that offer high-level views of enterprise services
> >>>> 3. A single system of record for all IT processes
> >>>> http://p.sf.net/sfu/servicenow-d2d-j
> >>>> _______________________________________________
> >>>> Postgres-xc-developers mailing list
> >>>> Pos...@li...
> >>>> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
> >>>>
> >>>>
> >>>>
> >>>>
> >>
> ------------------------------------------------------------------------------
> >>>> How ServiceNow helps IT people transform IT departments:
> >>>> 1. A cloud service to automate IT design, transition and operations
> >>>> 2. Dashboards that offer high-level views of enterprise services
> >>>> 3. A single system of record for all IT processes
> >>>> http://p.sf.net/sfu/servicenow-d2d-j
> >>>> _______________________________________________
> >>>> Postgres-xc-developers mailing list
> >>>> Pos...@li...
> >>>> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> --------------------------------------------
> >>>> NTTソフトウェア株式会社
> >>>> 技術開発センター OSS基盤技術部門
> >>>> 勝俣 智成
> >>>> TEL：045-212-7665
> >>>> FAX：045-662-7856
> >>>> E-Mail: kat...@po...
> >>>> --------------------------------------------
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> Best Wishes,
> >>>> Ashutosh Bapat
> >>>> EntepriseDB Corporation
> >>>> The Postgres Database Company
> >>>>
> >>
> ------------------------------------------------------------------------------
> >>>> How ServiceNow helps IT people transform IT departments:
> >>>> 1. A cloud service to automate IT design, transition and operations
> >>>> 2. Dashboards that offer high-level views of enterprise services
> >>>> 3. A single system of record for all IT processes
> >>>>
> >>
> http://p.sf.net/sfu/servicenow-d2d-j_______________________________________________
> >>>> Postgres-xc-developers mailing list
> >>>> Pos...@li...
> >>>> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
> >>>
> >>
> >>
> >>
> >>
> ------------------------------------------------------------------------------
> >> How ServiceNow helps IT people transform IT departments:
> >> 1. A cloud service to automate IT design, transition and operations
> >> 2. Dashboards that offer high-level views of enterprise services
> >> 3. A single system of record for all IT processes
> >> http://p.sf.net/sfu/servicenow-d2d-j
> >> _______________________________________________
> >> Postgres-xc-developers mailing list
> >> Pos...@li...
> >> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
> >>
> >
> >
> > --
> > --------------------------------------------
> > NTTソフトウェア株式会社
> >  技術開発センター OSS基盤技術部門
> >  勝俣 智成
> > TEL：045-212-7665
> > FAX：045-662-7856
> > E-Mail: kat...@po...
> > --------------------------------------------
> >
> >
> >
> >
> ------------------------------------------------------------------------------
> > How ServiceNow helps IT people transform IT departments:
> > 1. A cloud service to automate IT design, transition and operations
> > 2. Dashboards that offer high-level views of enterprise services
> > 3. A single system of record for all IT processes
> > http://p.sf.net/sfu/servicenow-d2d-j
> > _______________________________________________
> > Postgres-xc-developers mailing list
> > Pos...@li...
> > https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
> >
>
>
>
> ------------------------------------------------------------------------------
> How ServiceNow helps IT people transform IT departments:
> 1. A cloud service to automate IT design, transition and operations
> 2. Dashboards that offer high-level views of enterprise services
> 3. A single system of record for all IT processes
> http://p.sf.net/sfu/servicenow-d2d-j
> _______________________________________________
> Postgres-xc-developers mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>

Yeah, I found that this command stuck and doing this by direct connection to datanode works.

Regards;
---
Koichi Suzuki



On 2013/06/05, at 18:12, Tomonari Katsumata <kat...@po...> wrote:

> Hi,
> 
> The queries sent by Suzuki-san work fine,
> but my problem is still there.
> Could you try execute the query I sent before?
> 
> ---
> EXECUTE DIRECT ON (data1) $$
> SELECT
> count(*)
> FROM
> (SELECT * FROM pg_locks l LEFT JOIN
> (SELECT * FROM pg_stat_activity) s ON l.database = s.datid) a
> $$
> ---
> 
> I don't change this query because it work with Postgres-XC v1.0.
> 
> regards,
> -------
> NTT Software Corporation
> Tomonari Katsumata
> 
> (2013/06/05 16:20), Tomonari Katsumata wrote:
>> Hi, all
>> 
>> thank you for many responses!
>> 
>> OK, I'll try it with the current master.
>> 
>> It seems that it'll work fine...
>> 
>> Sorry for bothering you.
>> 
>> regards,
>> --------
>> NTT Software Corporation
>> Tomonari Katsumata
>> 
>> 
>> (2013/06/05 13:48), 鈴木 幸市 wrote:
>>> Now snapshot warning is disabled. Michael committed this patch.
>>> 
>>> I tested the query with the current master as of this noon and I got
>> (probably) correct result.
>>> Here's the result:
>>> 
>>> koichi=# execute direct on (datanode1) $$
>>> select count(*) from (select * from pg_locks) l left join
>>> (select * from pg_stat_activity) s on (l.database=s.datid);
>>> $$;
>>> count
>>> -------
>>> 9
>>> (1 row)
>>> 
>>> koichi=# \q
>>> …
>>> 
>>> koichi=# execute direct on (datanode1) $$
>>> koichi$# select count(*) from pg_locks l left join pg_stat_activity s
>>> koichi$# on (l.database=s.datid);
>>> koichi$# $$;
>>> count
>>> -------
>>> 11
>>> (1 row)
>>> 
>>> koichi=#
>>> 
>>> Second statement is simpler version. Anyway, they seem to work find.
>>> 
>>> Katsumata-san, could you try this with the latest head? It is
>> available both from sourceforge and github.
>>> Regards;
>>> ---
>>> Koichi Suzuki
>>> 
>>> 
>>> 
>>> On 2013/06/05, at 13:39, Ashutosh Bapat
>> <ash...@en...> wrote:
>>>> 
>>>> 
>>>> On Wed, Jun 5, 2013 at 9:57 AM, Tomonari Katsumata
>> <kat...@po...> wrote:
>>>> Hi Suzuki-san, Ashutosh,
>>>> 
>>>>> Suzuki-san
>>>> I don't make any user tables.
>>>> As the simple example I sent before, I use only system-catalogs.
>>>> 
>>>>> Ashtosh
>>>> I'm developing database monitor tool and
>>>> I use "EXECUTE DIRECT" to get database statistics data from
>>>> particular coordinator/datanode.
>>>> 
>>>> :) huh
>>>> 
>>>> I think, monitoring tools should directly query the datanodes or
>> coordinators. You will get snapshot warning, but that can be ignored I
>> guess. If they start querying coordinators, there will be performance
>> drop since coordinators directly handle the clients.
>>>> Any other thoughts?
>>>> regard,
>>>> 
>>>> ---------
>>>> NTT Software Corporation
>>>> Tomonari Katsumata
>>>> 
>>>> (2013/06/04 13:10), Ashutosh Bapat wrote:
>>>> Hi Tomonari,
>>>> 
>>>> Thanks for the bug report.
>>>> 
>>>> I am curious to know, what's the purpose of using EXECUTE DIRECT? We
>>>> discourage using Execute Direct in the applications. It's only for
>>>> debugging purposes.
>>>> 
>>>> 
>>>> On Tue, Jun 4, 2013 at 7:28 AM, Koichi Suzuki
>> <koi...@gm...>wrote:
>>>> Thank you Katsumata-san for the report.
>>>> 
>>>> Could you provide CREATE TABLE statement for each table involved with
>> some
>>>> of the data?
>>>> 
>>>> I will ad this to the bug tracker after I recreate the issue.
>>>> 
>>>> Best Regards;
>>>> 
>>>> ----------
>>>> Koichi Suzuki
>>>> 
>>>> 
>>>> 2013/6/4 Tomonari Katsumata <kat...@po...>
>>>> 
>>>> Hi, I have a problem with query executing.
>>>> 
>>>> I cant't have any response when I execute a query.
>>>> This problem occurs when some conditions are met.
>>>> 
>>>> The conditions are below.
>>>> ---------------------------------------------------------------------
>>>> 1. Issuing "EXECUTE DIRECT" to Datanode(ofcourse, via Coordinator).
>>>> 
>>>> 2. The Query Executing on Datanode has subquery on its FROM-clause.
>>>> 
>>>> 3. In the subquery, it has a JOIN clause.
>>>> 
>>>> 4. The Join clause is consisted with another subquery.
>>>> ---------------------------------------------------------------------
>>>> 
>>>> 
>>>> Simple example query is below.
>>>> ---------------------------------------------------------------
>>>> EXECUTE DIRECT ON (data1) $$
>>>> SELECT
>>>> count(*)
>>>> FROM
>>>> (SELECT * FROM pg_locks l LEFT JOIN
>>>> (SELECT * FROM pg_stat_activity) s ON l.database = s.datid) a
>>>> $$
>>>> ---------------------------------------------------------------
>>>> 
>>>> FYI:
>>>> This query works fine with Postgres-XC 1.0.3.
>>>> Is this already known bug ?
>>>> 
>>>> 
>>>> How can I avoid this problem ?
>>>> And what kind of info do you need to investigate it ?
>>>> 
>>>> ----------
>>>> NTT Software Corporation
>>>> Tomonari Katsumata
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>> ------------------------------------------------------------------------------
>>>> How ServiceNow helps IT people transform IT departments:
>>>> 1. A cloud service to automate IT design, transition and operations
>>>> 2. Dashboards that offer high-level views of enterprise services
>>>> 3. A single system of record for all IT processes
>>>> http://p.sf.net/sfu/servicenow-d2d-j
>>>> _______________________________________________
>>>> Postgres-xc-developers mailing list
>>>> Pos...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>>>> 
>>>> 
>>>> 
>>>> 
>> ------------------------------------------------------------------------------
>>>> How ServiceNow helps IT people transform IT departments:
>>>> 1. A cloud service to automate IT design, transition and operations
>>>> 2. Dashboards that offer high-level views of enterprise services
>>>> 3. A single system of record for all IT processes
>>>> http://p.sf.net/sfu/servicenow-d2d-j
>>>> _______________________________________________
>>>> Postgres-xc-developers mailing list
>>>> Pos...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> --
>>>> --------------------------------------------
>>>> NTTソフトウェア株式会社
>>>> 技術開発センター OSS基盤技術部門
>>>> 勝俣 智成
>>>> TEL：045-212-7665
>>>> FAX：045-662-7856
>>>> E-Mail: kat...@po...
>>>> --------------------------------------------
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> --
>>>> Best Wishes,
>>>> Ashutosh Bapat
>>>> EntepriseDB Corporation
>>>> The Postgres Database Company
>>>> 
>> ------------------------------------------------------------------------------
>>>> How ServiceNow helps IT people transform IT departments:
>>>> 1. A cloud service to automate IT design, transition and operations
>>>> 2. Dashboards that offer high-level views of enterprise services
>>>> 3. A single system of record for all IT processes
>>>> 
>> http://p.sf.net/sfu/servicenow-d2d-j_______________________________________________
>>>> Postgres-xc-developers mailing list
>>>> Pos...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>>> 
>> 
>> 
>> 
>> ------------------------------------------------------------------------------
>> How ServiceNow helps IT people transform IT departments:
>> 1. A cloud service to automate IT design, transition and operations
>> 2. Dashboards that offer high-level views of enterprise services
>> 3. A single system of record for all IT processes
>> http://p.sf.net/sfu/servicenow-d2d-j
>> _______________________________________________
>> Postgres-xc-developers mailing list
>> Pos...@li...
>> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>> 
> 
> 
> -- 
> --------------------------------------------
> NTTソフトウェア株式会社
>  技術開発センター OSS基盤技術部門
>  勝俣 智成
> TEL：045-212-7665
> FAX：045-662-7856
> E-Mail: kat...@po...
> --------------------------------------------
> 
> 
> 
> ------------------------------------------------------------------------------
> How ServiceNow helps IT people transform IT departments:
> 1. A cloud service to automate IT design, transition and operations
> 2. Dashboards that offer high-level views of enterprise services
> 3. A single system of record for all IT processes
> http://p.sf.net/sfu/servicenow-d2d-j
> _______________________________________________
> Postgres-xc-developers mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
> 

Hi,

The queries sent by Suzuki-san work fine,
but my problem is still there.
Could you try execute the query I sent before?

---
EXECUTE DIRECT ON (data1) $$
SELECT
count(*)
FROM
(SELECT * FROM pg_locks l LEFT JOIN
(SELECT * FROM pg_stat_activity) s ON l.database = s.datid) a
$$
---

I don't change this query because it work with Postgres-XC v1.0.

regards,
-------
NTT Software Corporation
Tomonari Katsumata

(2013/06/05 16:20), Tomonari Katsumata wrote:
> Hi, all
>
> thank you for many responses!
>
> OK, I'll try it with the current master.
>
> It seems that it'll work fine...
>
> Sorry for bothering you.
>
> regards,
> --------
> NTT Software Corporation
> Tomonari Katsumata
>
>
> (2013/06/05 13:48), 鈴木 幸市 wrote:
>> Now snapshot warning is disabled. Michael committed this patch.
>>
>> I tested the query with the current master as of this noon and I got
> (probably) correct result.
>> Here's the result:
>>
>> koichi=# execute direct on (datanode1) $$
>> select count(*) from (select * from pg_locks) l left join
>> (select * from pg_stat_activity) s on (l.database=s.datid);
>> $$;
>> count
>> -------
>> 9
>> (1 row)
>>
>> koichi=# \q
>> …
>>
>> koichi=# execute direct on (datanode1) $$
>> koichi$# select count(*) from pg_locks l left join pg_stat_activity s
>> koichi$# on (l.database=s.datid);
>> koichi$# $$;
>> count
>> -------
>> 11
>> (1 row)
>>
>> koichi=#
>>
>> Second statement is simpler version. Anyway, they seem to work find.
>>
>> Katsumata-san, could you try this with the latest head? It is
> available both from sourceforge and github.
>> Regards;
>> ---
>> Koichi Suzuki
>>
>>
>>
>> On 2013/06/05, at 13:39, Ashutosh Bapat
> <ash...@en...> wrote:
>>>
>>>
>>> On Wed, Jun 5, 2013 at 9:57 AM, Tomonari Katsumata
> <kat...@po...> wrote:
>>> Hi Suzuki-san, Ashutosh,
>>>
>>>> Suzuki-san
>>> I don't make any user tables.
>>> As the simple example I sent before, I use only system-catalogs.
>>>
>>>> Ashtosh
>>> I'm developing database monitor tool and
>>> I use "EXECUTE DIRECT" to get database statistics data from
>>> particular coordinator/datanode.
>>>
>>> :) huh
>>>
>>> I think, monitoring tools should directly query the datanodes or
> coordinators. You will get snapshot warning, but that can be ignored I
> guess. If they start querying coordinators, there will be performance
> drop since coordinators directly handle the clients.
>>> Any other thoughts?
>>> regard,
>>>
>>> ---------
>>> NTT Software Corporation
>>> Tomonari Katsumata
>>>
>>> (2013/06/04 13:10), Ashutosh Bapat wrote:
>>> Hi Tomonari,
>>>
>>> Thanks for the bug report.
>>>
>>> I am curious to know, what's the purpose of using EXECUTE DIRECT? We
>>> discourage using Execute Direct in the applications. It's only for
>>> debugging purposes.
>>>
>>>
>>> On Tue, Jun 4, 2013 at 7:28 AM, Koichi Suzuki
> <koi...@gm...>wrote:
>>> Thank you Katsumata-san for the report.
>>>
>>> Could you provide CREATE TABLE statement for each table involved with
> some
>>> of the data?
>>>
>>> I will ad this to the bug tracker after I recreate the issue.
>>>
>>> Best Regards;
>>>
>>> ----------
>>> Koichi Suzuki
>>>
>>>
>>> 2013/6/4 Tomonari Katsumata <kat...@po...>
>>>
>>> Hi, I have a problem with query executing.
>>>
>>> I cant't have any response when I execute a query.
>>> This problem occurs when some conditions are met.
>>>
>>> The conditions are below.
>>> ---------------------------------------------------------------------
>>> 1. Issuing "EXECUTE DIRECT" to Datanode(ofcourse, via Coordinator).
>>>
>>> 2. The Query Executing on Datanode has subquery on its FROM-clause.
>>>
>>> 3. In the subquery, it has a JOIN clause.
>>>
>>> 4. The Join clause is consisted with another subquery.
>>> ---------------------------------------------------------------------
>>>
>>>
>>> Simple example query is below.
>>> ---------------------------------------------------------------
>>> EXECUTE DIRECT ON (data1) $$
>>> SELECT
>>> count(*)
>>> FROM
>>> (SELECT * FROM pg_locks l LEFT JOIN
>>> (SELECT * FROM pg_stat_activity) s ON l.database = s.datid) a
>>> $$
>>> ---------------------------------------------------------------
>>>
>>> FYI:
>>> This query works fine with Postgres-XC 1.0.3.
>>> Is this already known bug ?
>>>
>>>
>>> How can I avoid this problem ?
>>> And what kind of info do you need to investigate it ?
>>>
>>> ----------
>>> NTT Software Corporation
>>> Tomonari Katsumata
>>>
>>>
>>>
>>>
>>>
> ------------------------------------------------------------------------------
>>> How ServiceNow helps IT people transform IT departments:
>>> 1. A cloud service to automate IT design, transition and operations
>>> 2. Dashboards that offer high-level views of enterprise services
>>> 3. A single system of record for all IT processes
>>> http://p.sf.net/sfu/servicenow-d2d-j
>>> _______________________________________________
>>> Postgres-xc-developers mailing list
>>> Pos...@li...
>>> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>>>
>>>
>>>
>>>
> ------------------------------------------------------------------------------
>>> How ServiceNow helps IT people transform IT departments:
>>> 1. A cloud service to automate IT design, transition and operations
>>> 2. Dashboards that offer high-level views of enterprise services
>>> 3. A single system of record for all IT processes
>>> http://p.sf.net/sfu/servicenow-d2d-j
>>> _______________________________________________
>>> Postgres-xc-developers mailing list
>>> Pos...@li...
>>> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>>>
>>>
>>>
>>>
>>>
>>> --
>>> --------------------------------------------
>>> NTTソフトウェア株式会社
>>> 技術開発センター OSS基盤技術部門
>>> 勝俣 智成
>>> TEL：045-212-7665
>>> FAX：045-662-7856
>>> E-Mail: kat...@po...
>>> --------------------------------------------
>>>
>>>
>>>
>>>
>>>
>>> --
>>> Best Wishes,
>>> Ashutosh Bapat
>>> EntepriseDB Corporation
>>> The Postgres Database Company
>>>
> ------------------------------------------------------------------------------
>>> How ServiceNow helps IT people transform IT departments:
>>> 1. A cloud service to automate IT design, transition and operations
>>> 2. Dashboards that offer high-level views of enterprise services
>>> 3. A single system of record for all IT processes
>>>
> http://p.sf.net/sfu/servicenow-d2d-j_______________________________________________
>>> Postgres-xc-developers mailing list
>>> Pos...@li...
>>> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>>
>
>
>
> ------------------------------------------------------------------------------
> How ServiceNow helps IT people transform IT departments:
> 1. A cloud service to automate IT design, transition and operations
> 2. Dashboards that offer high-level views of enterprise services
> 3. A single system of record for all IT processes
> http://p.sf.net/sfu/servicenow-d2d-j
> _______________________________________________
> Postgres-xc-developers mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>


-- 
--------------------------------------------
NTTソフトウェア株式会社
  技術開発センター OSS基盤技術部門
  勝俣 智成
TEL：045-212-7665
FAX：045-662-7856
E-Mail: kat...@po...
--------------------------------------------

You are very welcome.

Please do not hesitate to post your problems/questions.

Regards;
---
Koichi Suzuki



On 2013/06/05, at 16:20, Tomonari Katsumata <kat...@po...> wrote:

> Hi, all
> 
> thank you for many responses!
> 
> OK, I'll try it with the current master.
> 
> It seems that it'll work fine...
> 
> Sorry for bothering you.
> 
> regards,
> --------
> NTT Software Corporation
> Tomonari Katsumata
> 
> 
> (2013/06/05 13:48), 鈴木 幸市 wrote:
>> Now snapshot warning is disabled. Michael committed this patch.
>> 
>> I tested the query with the current master as of this noon and I got
> (probably) correct result.
>> 
>> Here's the result:
>> 
>> koichi=# execute direct on (datanode1) $$
>> select count(*) from (select * from pg_locks) l left join
>> (select * from pg_stat_activity) s on (l.database=s.datid);
>> $$;
>> count
>> -------
>> 9
>> (1 row)
>> 
>> koichi=# \q
>> …
>> 
>> koichi=# execute direct on (datanode1) $$
>> koichi$# select count(*) from pg_locks l left join pg_stat_activity s
>> koichi$# on (l.database=s.datid);
>> koichi$# $$;
>> count
>> -------
>> 11
>> (1 row)
>> 
>> koichi=#
>> 
>> Second statement is simpler version. Anyway, they seem to work find.
>> 
>> Katsumata-san, could you try this with the latest head? It is
> available both from sourceforge and github.
>> 
>> Regards;
>> ---
>> Koichi Suzuki
>> 
>> 
>> 
>> On 2013/06/05, at 13:39, Ashutosh Bapat
> <ash...@en...> wrote:
>> 
>>> 
>>> 
>>> 
>>> On Wed, Jun 5, 2013 at 9:57 AM, Tomonari Katsumata
> <kat...@po...> wrote:
>>> Hi Suzuki-san, Ashutosh,
>>> 
>>>> Suzuki-san
>>> I don't make any user tables.
>>> As the simple example I sent before, I use only system-catalogs.
>>> 
>>>> Ashtosh
>>> I'm developing database monitor tool and
>>> I use "EXECUTE DIRECT" to get database statistics data from
>>> particular coordinator/datanode.
>>> 
>>> :) huh
>>> 
>>> I think, monitoring tools should directly query the datanodes or
> coordinators. You will get snapshot warning, but that can be ignored I
> guess. If they start querying coordinators, there will be performance
> drop since coordinators directly handle the clients.
>>> 
>>> Any other thoughts?
>>> regard,
>>> 
>>> ---------
>>> NTT Software Corporation
>>> Tomonari Katsumata
>>> 
>>> (2013/06/04 13:10), Ashutosh Bapat wrote:
>>> Hi Tomonari,
>>> 
>>> Thanks for the bug report.
>>> 
>>> I am curious to know, what's the purpose of using EXECUTE DIRECT? We
>>> discourage using Execute Direct in the applications. It's only for
>>> debugging purposes.
>>> 
>>> 
>>> On Tue, Jun 4, 2013 at 7:28 AM, Koichi Suzuki
> <koi...@gm...>wrote:
>>> 
>>> Thank you Katsumata-san for the report.
>>> 
>>> Could you provide CREATE TABLE statement for each table involved with
> some
>>> of the data?
>>> 
>>> I will ad this to the bug tracker after I recreate the issue.
>>> 
>>> Best Regards;
>>> 
>>> ----------
>>> Koichi Suzuki
>>> 
>>> 
>>> 2013/6/4 Tomonari Katsumata <kat...@po...>
>>> 
>>> Hi, I have a problem with query executing.
>>> 
>>> I cant't have any response when I execute a query.
>>> This problem occurs when some conditions are met.
>>> 
>>> The conditions are below.
>>> ---------------------------------------------------------------------
>>> 1. Issuing "EXECUTE DIRECT" to Datanode(ofcourse, via Coordinator).
>>> 
>>> 2. The Query Executing on Datanode has subquery on its FROM-clause.
>>> 
>>> 3. In the subquery, it has a JOIN clause.
>>> 
>>> 4. The Join clause is consisted with another subquery.
>>> ---------------------------------------------------------------------
>>> 
>>> 
>>> Simple example query is below.
>>> ---------------------------------------------------------------
>>> EXECUTE DIRECT ON (data1) $$
>>> SELECT
>>> count(*)
>>> FROM
>>> (SELECT * FROM pg_locks l LEFT JOIN
>>> (SELECT * FROM pg_stat_activity) s ON l.database = s.datid) a
>>> $$
>>> ---------------------------------------------------------------
>>> 
>>> FYI:
>>> This query works fine with Postgres-XC 1.0.3.
>>> Is this already known bug ?
>>> 
>>> 
>>> How can I avoid this problem ?
>>> And what kind of info do you need to investigate it ?
>>> 
>>> ----------
>>> NTT Software Corporation
>>> Tomonari Katsumata
>>> 
>>> 
>>> 
>>> 
>>> 
> ------------------------------------------------------------------------------
>>> How ServiceNow helps IT people transform IT departments:
>>> 1. A cloud service to automate IT design, transition and operations
>>> 2. Dashboards that offer high-level views of enterprise services
>>> 3. A single system of record for all IT processes
>>> http://p.sf.net/sfu/servicenow-d2d-j
>>> _______________________________________________
>>> Postgres-xc-developers mailing list
>>> Pos...@li...
>>> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>>> 
>>> 
>>> 
>>> 
> ------------------------------------------------------------------------------
>>> How ServiceNow helps IT people transform IT departments:
>>> 1. A cloud service to automate IT design, transition and operations
>>> 2. Dashboards that offer high-level views of enterprise services
>>> 3. A single system of record for all IT processes
>>> http://p.sf.net/sfu/servicenow-d2d-j
>>> _______________________________________________
>>> Postgres-xc-developers mailing list
>>> Pos...@li...
>>> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>>> 
>>> 
>>> 
>>> 
>>> 
>>> --
>>> --------------------------------------------
>>> NTTソフトウェア株式会社
>>> 技術開発センター OSS基盤技術部門
>>> 勝俣 智成
>>> TEL：045-212-7665
>>> FAX：045-662-7856
>>> E-Mail: kat...@po...
>>> --------------------------------------------
>>> 
>>> 
>>> 
>>> 
>>> 
>>> --
>>> Best Wishes,
>>> Ashutosh Bapat
>>> EntepriseDB Corporation
>>> The Postgres Database Company
>>> 
> ------------------------------------------------------------------------------
>>> How ServiceNow helps IT people transform IT departments:
>>> 1. A cloud service to automate IT design, transition and operations
>>> 2. Dashboards that offer high-level views of enterprise services
>>> 3. A single system of record for all IT processes
>>> 
> http://p.sf.net/sfu/servicenow-d2d-j_______________________________________________
>>> Postgres-xc-developers mailing list
>>> Pos...@li...
>>> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>> 
>> 
> 
> 
> 
> 

Hi, all

thank you for many responses!

OK, I'll try it with the current master.

It seems that it'll work fine...

Sorry for bothering you.

regards,
--------
NTT Software Corporation
Tomonari Katsumata


(2013/06/05 13:48), 鈴木 幸市 wrote:
> Now snapshot warning is disabled. Michael committed this patch.
>
> I tested the query with the current master as of this noon and I got
(probably) correct result.
>
> Here's the result:
>
> koichi=# execute direct on (datanode1) $$
> select count(*) from (select * from pg_locks) l left join
> (select * from pg_stat_activity) s on (l.database=s.datid);
> $$;
> count
> -------
> 9
> (1 row)
>
> koichi=# \q
> …
>
> koichi=# execute direct on (datanode1) $$
> koichi$# select count(*) from pg_locks l left join pg_stat_activity s
> koichi$# on (l.database=s.datid);
> koichi$# $$;
> count
> -------
> 11
> (1 row)
>
> koichi=#
>
> Second statement is simpler version. Anyway, they seem to work find.
>
> Katsumata-san, could you try this with the latest head? It is
available both from sourceforge and github.
>
> Regards;
> ---
> Koichi Suzuki
>
>
>
> On 2013/06/05, at 13:39, Ashutosh Bapat
<ash...@en...> wrote:
>
>>
>>
>>
>> On Wed, Jun 5, 2013 at 9:57 AM, Tomonari Katsumata
<kat...@po...> wrote:
>> Hi Suzuki-san, Ashutosh,
>>
>>> Suzuki-san
>> I don't make any user tables.
>> As the simple example I sent before, I use only system-catalogs.
>>
>>> Ashtosh
>> I'm developing database monitor tool and
>> I use "EXECUTE DIRECT" to get database statistics data from
>> particular coordinator/datanode.
>>
>> :) huh
>>
>> I think, monitoring tools should directly query the datanodes or
coordinators. You will get snapshot warning, but that can be ignored I
guess. If they start querying coordinators, there will be performance
drop since coordinators directly handle the clients.
>>
>> Any other thoughts?
>> regard,
>>
>> ---------
>> NTT Software Corporation
>> Tomonari Katsumata
>>
>> (2013/06/04 13:10), Ashutosh Bapat wrote:
>> Hi Tomonari,
>>
>> Thanks for the bug report.
>>
>> I am curious to know, what's the purpose of using EXECUTE DIRECT? We
>> discourage using Execute Direct in the applications. It's only for
>> debugging purposes.
>>
>>
>> On Tue, Jun 4, 2013 at 7:28 AM, Koichi Suzuki
<koi...@gm...>wrote:
>>
>> Thank you Katsumata-san for the report.
>>
>> Could you provide CREATE TABLE statement for each table involved with
some
>> of the data?
>>
>> I will ad this to the bug tracker after I recreate the issue.
>>
>> Best Regards;
>>
>> ----------
>> Koichi Suzuki
>>
>>
>> 2013/6/4 Tomonari Katsumata <kat...@po...>
>>
>> Hi, I have a problem with query executing.
>>
>> I cant't have any response when I execute a query.
>> This problem occurs when some conditions are met.
>>
>> The conditions are below.
>> ---------------------------------------------------------------------
>> 1. Issuing "EXECUTE DIRECT" to Datanode(ofcourse, via Coordinator).
>>
>> 2. The Query Executing on Datanode has subquery on its FROM-clause.
>>
>> 3. In the subquery, it has a JOIN clause.
>>
>> 4. The Join clause is consisted with another subquery.
>> ---------------------------------------------------------------------
>>
>>
>> Simple example query is below.
>> ---------------------------------------------------------------
>> EXECUTE DIRECT ON (data1) $$
>> SELECT
>> count(*)
>> FROM
>> (SELECT * FROM pg_locks l LEFT JOIN
>> (SELECT * FROM pg_stat_activity) s ON l.database = s.datid) a
>> $$
>> ---------------------------------------------------------------
>>
>> FYI:
>> This query works fine with Postgres-XC 1.0.3.
>> Is this already known bug ?
>>
>>
>> How can I avoid this problem ?
>> And what kind of info do you need to investigate it ?
>>
>> ----------
>> NTT Software Corporation
>> Tomonari Katsumata
>>
>>
>>
>>
>>
------------------------------------------------------------------------------
>> How ServiceNow helps IT people transform IT departments:
>> 1. A cloud service to automate IT design, transition and operations
>> 2. Dashboards that offer high-level views of enterprise services
>> 3. A single system of record for all IT processes
>> http://p.sf.net/sfu/servicenow-d2d-j
>> _______________________________________________
>> Postgres-xc-developers mailing list
>> Pos...@li...
>> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>>
>>
>>
>>
------------------------------------------------------------------------------
>> How ServiceNow helps IT people transform IT departments:
>> 1. A cloud service to automate IT design, transition and operations
>> 2. Dashboards that offer high-level views of enterprise services
>> 3. A single system of record for all IT processes
>> http://p.sf.net/sfu/servicenow-d2d-j
>> _______________________________________________
>> Postgres-xc-developers mailing list
>> Pos...@li...
>> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>>
>>
>>
>>
>>
>> --
>> --------------------------------------------
>> NTTソフトウェア株式会社
>> 技術開発センター OSS基盤技術部門
>> 勝俣 智成
>> TEL：045-212-7665
>> FAX：045-662-7856
>> E-Mail: kat...@po...
>> --------------------------------------------
>>
>>
>>
>>
>>
>> --
>> Best Wishes,
>> Ashutosh Bapat
>> EntepriseDB Corporation
>> The Postgres Database Company
>>
------------------------------------------------------------------------------
>> How ServiceNow helps IT people transform IT departments:
>> 1. A cloud service to automate IT design, transition and operations
>> 2. Dashboards that offer high-level views of enterprise services
>> 3. A single system of record for all IT processes
>>
http://p.sf.net/sfu/servicenow-d2d-j_______________________________________________
>> Postgres-xc-developers mailing list
>> Pos...@li...
>> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>
>

Thanks Michael for the input.   This is what I remembered.
---
Koichi Suzuki



On 2013/06/05, at 14:03, Michael Paquier <mic...@gm...> wrote:

> 
> 
> 
> On Wed, Jun 5, 2013 at 1:39 PM, Ashutosh Bapat <ash...@en...> wrote:
> 
> 
> 
> On Wed, Jun 5, 2013 at 9:57 AM, Tomonari Katsumata <kat...@po...> wrote:
> Hi Suzuki-san, Ashutosh,
> 
> >Suzuki-san
> I don't make any user tables.
> As the simple example I sent before, I use only system-catalogs.
> 
> >Ashtosh
> I'm developing database monitor tool and
> I use "EXECUTE DIRECT" to get database statistics data from
> particular coordinator/datanode.
> 
> :) huh 
> 
> I think, monitoring tools should directly query the datanodes or coordinators. You will get snapshot warning, but that can be ignored I guess.
> Worth mentioning that it is not the case for 1.1:
> https://github.com/postgres-xc/postgres-xc/commit/fe9985c168d85738e5d88ed9407b840449f31b75 
> You get a clean snapshot for read queries run directly from Datanodes.
> 
> If they start querying coordinators, there will be performance drop since coordinators directly handle the clients.
> Yep.
> -- 
> Michael
> ------------------------------------------------------------------------------
> How ServiceNow helps IT people transform IT departments:
> 1. A cloud service to automate IT design, transition and operations
> 2. Dashboards that offer high-level views of enterprise services
> 3. A single system of record for all IT processes
> http://p.sf.net/sfu/servicenow-d2d-j_______________________________________________
> Postgres-xc-developers mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers

On Wed, Jun 5, 2013 at 1:39 PM, Ashutosh Bapat <
ash...@en...> wrote:

>
>
>
> On Wed, Jun 5, 2013 at 9:57 AM, Tomonari Katsumata <
> kat...@po...> wrote:
>
>> Hi Suzuki-san, Ashutosh,
>>
>> >Suzuki-san
>> I don't make any user tables.
>> As the simple example I sent before, I use only system-catalogs.
>>
>> >Ashtosh
>> I'm developing database monitor tool and
>> I use "EXECUTE DIRECT" to get database statistics data from
>> particular coordinator/datanode.
>>
>> :) huh
>
> I think, monitoring tools should directly query the datanodes or
> coordinators. You will get snapshot warning, but that can be ignored I
> guess.
>
Worth mentioning that it is not the case for 1.1:
https://github.com/postgres-xc/postgres-xc/commit/fe9985c168d85738e5d88ed9407b840449f31b75
You get a clean snapshot for read queries run directly from Datanodes.

If they start querying coordinators, there will be performance drop since
> coordinators directly handle the clients.
>
Yep.
-- 
Michael

Snapshot warning comes when you connect directly to the datanode and not
when an execute direct is issued for a datanode. That warning is still
there.

    if (IS_PGXC_DATANODE && !isRestoreMode &&
        snapshot_source == SNAPSHOT_UNDEFINED &&
        IsPostmasterEnvironment &&
        IsNormalProcessingMode() &&
        !IsAutoVacuumLauncherProcess())
    {
        elog(WARNING, "Do not have a GTM snapshot available");
    }


On Wed, Jun 5, 2013 at 9:48 AM, 鈴木 幸市 <ko...@in...> wrote:

> Now snapshot warning is disabled.  Michael committed this patch.
>
> I tested the query with the current master as of this noon and I got
> (probably) correct result.
>
> Here's the result:
>
> koichi=# execute direct on (datanode1) $$
> select count(*) from (select * from pg_locks) l left join
> (select * from pg_stat_activity) s on (l.database=s.datid);
> $$;
>  count
> -------
>      9
> (1 row)
>
> koichi=# \q
> …
>
> koichi=# execute direct on (datanode1) $$
> koichi$# select count(*) from pg_locks l left join pg_stat_activity s
> koichi$# on (l.database=s.datid);
> koichi$# $$;
>  count
> -------
>     11
> (1 row)
>
> koichi=#
>
> Second statement is simpler version.   Anyway, they seem to work find.
>
> Katsumata-san, could you try this with the latest head?  It is available
> both from sourceforge and github.
>
> Regards;
> ---
> Koichi Suzuki
>
>
>
> On 2013/06/05, at 13:39, Ashutosh Bapat <ash...@en...>
> wrote:
>
>
>
>
> On Wed, Jun 5, 2013 at 9:57 AM, Tomonari Katsumata <
> kat...@po...> wrote:
>
>> Hi Suzuki-san, Ashutosh,
>>
>> >Suzuki-san
>> I don't make any user tables.
>> As the simple example I sent before, I use only system-catalogs.
>>
>> >Ashtosh
>> I'm developing database monitor tool and
>> I use "EXECUTE DIRECT" to get database statistics data from
>> particular coordinator/datanode.
>>
>> :) huh
>
> I think, monitoring tools should directly query the datanodes or
> coordinators. You will get snapshot warning, but that can be ignored I
> guess. If they start querying coordinators, there will be performance drop
> since coordinators directly handle the clients.
>
> Any other thoughts?
>
>> regard,
>>
>> ---------
>> NTT Software Corporation
>> Tomonari Katsumata
>>
>> (2013/06/04 13:10), Ashutosh Bapat wrote:
>>
>>> Hi Tomonari,
>>>
>>> Thanks for the bug report.
>>>
>>> I am curious to know, what's the purpose of using EXECUTE DIRECT? We
>>> discourage using Execute Direct in the applications. It's only for
>>> debugging purposes.
>>>
>>>
>>> On Tue, Jun 4, 2013 at 7:28 AM, Koichi Suzuki <koi...@gm...
>>> >**wrote:
>>>
>>>  Thank you Katsumata-san for the report.
>>>>
>>>> Could you provide CREATE TABLE statement for each table involved with
>>>> some
>>>> of the data?
>>>>
>>>> I will ad this to the bug tracker after I recreate the issue.
>>>>
>>>> Best Regards;
>>>>
>>>> ----------
>>>> Koichi Suzuki
>>>>
>>>>
>>>> 2013/6/4 Tomonari Katsumata <katsumata.tomonari@po.ntts.**co.jp<kat...@po...>
>>>> >
>>>>
>>>>  Hi, I have a problem with query executing.
>>>>>
>>>>> I cant't have any response when I execute a query.
>>>>> This problem occurs when some conditions are met.
>>>>>
>>>>> The conditions are below.
>>>>> ------------------------------**------------------------------**
>>>>> ---------
>>>>> 1. Issuing "EXECUTE DIRECT" to Datanode(ofcourse, via Coordinator).
>>>>>
>>>>> 2. The Query Executing on Datanode has subquery on its FROM-clause.
>>>>>
>>>>> 3. In the subquery, it has a JOIN clause.
>>>>>
>>>>> 4. The Join clause is consisted with another subquery.
>>>>> ------------------------------**------------------------------**
>>>>> ---------
>>>>>
>>>>>
>>>>> Simple example query is below.
>>>>> ------------------------------**------------------------------**---
>>>>> EXECUTE DIRECT ON (data1) $$
>>>>> SELECT
>>>>> count(*)
>>>>> FROM
>>>>> (SELECT * FROM pg_locks l LEFT JOIN
>>>>> (SELECT * FROM pg_stat_activity) s ON l.database = s.datid) a
>>>>> $$
>>>>> ------------------------------**------------------------------**---
>>>>>
>>>>> FYI:
>>>>> This query works fine with Postgres-XC 1.0.3.
>>>>> Is this already known bug ?
>>>>>
>>>>>
>>>>> How can I avoid this problem ?
>>>>> And what kind of info do you need to investigate it ?
>>>>>
>>>>> ----------
>>>>> NTT Software Corporation
>>>>> Tomonari Katsumata
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> ------------------------------**------------------------------**
>>>>> ------------------
>>>>> How ServiceNow helps IT people transform IT departments:
>>>>> 1. A cloud service to automate IT design, transition and operations
>>>>> 2. Dashboards that offer high-level views of enterprise services
>>>>> 3. A single system of record for all IT processes
>>>>> http://p.sf.net/sfu/**servicenow-d2d-j<http://p.sf.net/sfu/servicenow-d2d-j>
>>>>> ______________________________**_________________
>>>>> Postgres-xc-developers mailing list
>>>>> Postgres-xc-developers@lists.**sourceforge.net<Pos...@li...>
>>>>> https://lists.sourceforge.net/**lists/listinfo/postgres-xc-**
>>>>> developers<https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers>
>>>>>
>>>>>
>>>>
>>>> ------------------------------**------------------------------**
>>>> ------------------
>>>> How ServiceNow helps IT people transform IT departments:
>>>> 1. A cloud service to automate IT design, transition and operations
>>>> 2. Dashboards that offer high-level views of enterprise services
>>>> 3. A single system of record for all IT processes
>>>> http://p.sf.net/sfu/**servicenow-d2d-j<http://p.sf.net/sfu/servicenow-d2d-j>
>>>> ______________________________**_________________
>>>> Postgres-xc-developers mailing list
>>>> Postgres-xc-developers@lists.**sourceforge.net<Pos...@li...>
>>>> https://lists.sourceforge.net/**lists/listinfo/postgres-xc-**developers<https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers>
>>>>
>>>>
>>>>
>>>
>>
>> --
>> ------------------------------**--------------
>> NTTソフトウェア株式会社
>>   技術開発センター OSS基盤技術部門
>>   勝俣 智成
>> TEL：045-212-7665
>> FAX：045-662-7856
>> E-Mail: kat...@po....**jp<kat...@po...>
>> ------------------------------**--------------
>>
>>
>>
>
>
> --
> Best Wishes,
> Ashutosh Bapat
> EntepriseDB Corporation
> The Postgres Database Company
> ------------------------------------------------------------------------------
> How ServiceNow helps IT people transform IT departments:
> 1. A cloud service to automate IT design, transition and operations
> 2. Dashboards that offer high-level views of enterprise services
> 3. A single system of record for all IT processes
>
> http://p.sf.net/sfu/servicenow-d2d-j_______________________________________________
> Postgres-xc-developers mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>
>
>
>
> ------------------------------------------------------------------------------
> How ServiceNow helps IT people transform IT departments:
> 1. A cloud service to automate IT design, transition and operations
> 2. Dashboards that offer high-level views of enterprise services
> 3. A single system of record for all IT processes
> http://p.sf.net/sfu/servicenow-d2d-j
> _______________________________________________
> Postgres-xc-developers mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>
>


-- 
-- 
*Abbas*
 Architect

Ph: 92.334.5100153
 Skype ID: gabbasb
www.enterprisedb.co
<http://www.enterprisedb.com/>m<http://www.enterprisedb.com/>
*
Follow us on Twitter*
@EnterpriseDB

Visit EnterpriseDB for tutorials, webinars,
whitepapers<http://www.enterprisedb.com/resources-community>and
more<http://www.enterprisedb.com/resources-community>

Now snapshot warning is disabled.  Michael committed this patch.

I tested the query with the current master as of this noon and I got (probably) correct result.

Here's the result:

koichi=# execute direct on (datanode1) $$
select count(*) from (select * from pg_locks) l left join
(select * from pg_stat_activity) s on (l.database=s.datid);
$$;
 count 
-------
     9
(1 row)

koichi=# \q
…

koichi=# execute direct on (datanode1) $$
koichi$# select count(*) from pg_locks l left join pg_stat_activity s
koichi$# on (l.database=s.datid);
koichi$# $$;
 count 
-------
    11
(1 row)

koichi=# 

Second statement is simpler version.   Anyway, they seem to work find.

Katsumata-san, could you try this with the latest head?  It is available both from sourceforge and github.

Regards;
---
Koichi Suzuki



On 2013/06/05, at 13:39, Ashutosh Bapat <ash...@en...> wrote:

> 
> 
> 
> On Wed, Jun 5, 2013 at 9:57 AM, Tomonari Katsumata <kat...@po...> wrote:
> Hi Suzuki-san, Ashutosh,
> 
> >Suzuki-san
> I don't make any user tables.
> As the simple example I sent before, I use only system-catalogs.
> 
> >Ashtosh
> I'm developing database monitor tool and
> I use "EXECUTE DIRECT" to get database statistics data from
> particular coordinator/datanode.
> 
> :) huh 
> 
> I think, monitoring tools should directly query the datanodes or coordinators. You will get snapshot warning, but that can be ignored I guess. If they start querying coordinators, there will be performance drop since coordinators directly handle the clients.
> 
> Any other thoughts?
> regard,
> 
> ---------
> NTT Software Corporation
> Tomonari Katsumata
> 
> (2013/06/04 13:10), Ashutosh Bapat wrote:
> Hi Tomonari,
> 
> Thanks for the bug report.
> 
> I am curious to know, what's the purpose of using EXECUTE DIRECT? We
> discourage using Execute Direct in the applications. It's only for
> debugging purposes.
> 
> 
> On Tue, Jun 4, 2013 at 7:28 AM, Koichi Suzuki <koi...@gm...>wrote:
> 
> Thank you Katsumata-san for the report.
> 
> Could you provide CREATE TABLE statement for each table involved with some
> of the data?
> 
> I will ad this to the bug tracker after I recreate the issue.
> 
> Best Regards;
> 
> ----------
> Koichi Suzuki
> 
> 
> 2013/6/4 Tomonari Katsumata <kat...@po...>
> 
> Hi, I have a problem with query executing.
> 
> I cant't have any response when I execute a query.
> This problem occurs when some conditions are met.
> 
> The conditions are below.
> ---------------------------------------------------------------------
> 1. Issuing "EXECUTE DIRECT" to Datanode(ofcourse, via Coordinator).
> 
> 2. The Query Executing on Datanode has subquery on its FROM-clause.
> 
> 3. In the subquery, it has a JOIN clause.
> 
> 4. The Join clause is consisted with another subquery.
> ---------------------------------------------------------------------
> 
> 
> Simple example query is below.
> ---------------------------------------------------------------
> EXECUTE DIRECT ON (data1) $$
> SELECT
> count(*)
> FROM
> (SELECT * FROM pg_locks l LEFT JOIN
> (SELECT * FROM pg_stat_activity) s ON l.database = s.datid) a
> $$
> ---------------------------------------------------------------
> 
> FYI:
> This query works fine with Postgres-XC 1.0.3.
> Is this already known bug ?
> 
> 
> How can I avoid this problem ?
> And what kind of info do you need to investigate it ?
> 
> ----------
> NTT Software Corporation
> Tomonari Katsumata
> 
> 
> 
> 
> ------------------------------------------------------------------------------
> How ServiceNow helps IT people transform IT departments:
> 1. A cloud service to automate IT design, transition and operations
> 2. Dashboards that offer high-level views of enterprise services
> 3. A single system of record for all IT processes
> http://p.sf.net/sfu/servicenow-d2d-j
> _______________________________________________
> Postgres-xc-developers mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
> 
> 
> 
> ------------------------------------------------------------------------------
> How ServiceNow helps IT people transform IT departments:
> 1. A cloud service to automate IT design, transition and operations
> 2. Dashboards that offer high-level views of enterprise services
> 3. A single system of record for all IT processes
> http://p.sf.net/sfu/servicenow-d2d-j
> _______________________________________________
> Postgres-xc-developers mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
> 
> 
> 
> 
> 
> -- 
> --------------------------------------------
> NTTソフトウェア株式会社
>   技術開発センター OSS基盤技術部門
>   勝俣 智成
> TEL：045-212-7665
> FAX：045-662-7856
> E-Mail: kat...@po...
> --------------------------------------------
> 
> 
> 
> 
> 
> -- 
> Best Wishes,
> Ashutosh Bapat
> EntepriseDB Corporation
> The Postgres Database Company
> ------------------------------------------------------------------------------
> How ServiceNow helps IT people transform IT departments:
> 1. A cloud service to automate IT design, transition and operations
> 2. Dashboards that offer high-level views of enterprise services
> 3. A single system of record for all IT processes
> http://p.sf.net/sfu/servicenow-d2d-j_______________________________________________
> Postgres-xc-developers mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers

On Wed, Jun 5, 2013 at 9:57 AM, Tomonari Katsumata <
kat...@po...> wrote:

> Hi Suzuki-san, Ashutosh,
>
> >Suzuki-san
> I don't make any user tables.
> As the simple example I sent before, I use only system-catalogs.
>
> >Ashtosh
> I'm developing database monitor tool and
> I use "EXECUTE DIRECT" to get database statistics data from
> particular coordinator/datanode.
>
> :) huh

I think, monitoring tools should directly query the datanodes or
coordinators. You will get snapshot warning, but that can be ignored I
guess. If they start querying coordinators, there will be performance drop
since coordinators directly handle the clients.

Any other thoughts?

> regard,
>
> ---------
> NTT Software Corporation
> Tomonari Katsumata
>
> (2013/06/04 13:10), Ashutosh Bapat wrote:
>
>> Hi Tomonari,
>>
>> Thanks for the bug report.
>>
>> I am curious to know, what's the purpose of using EXECUTE DIRECT? We
>> discourage using Execute Direct in the applications. It's only for
>> debugging purposes.
>>
>>
>> On Tue, Jun 4, 2013 at 7:28 AM, Koichi Suzuki <koi...@gm...>
>> **wrote:
>>
>>  Thank you Katsumata-san for the report.
>>>
>>> Could you provide CREATE TABLE statement for each table involved with
>>> some
>>> of the data?
>>>
>>> I will ad this to the bug tracker after I recreate the issue.
>>>
>>> Best Regards;
>>>
>>> ----------
>>> Koichi Suzuki
>>>
>>>
>>> 2013/6/4 Tomonari Katsumata <katsumata.tomonari@po.ntts.**co.jp<kat...@po...>
>>> >
>>>
>>>  Hi, I have a problem with query executing.
>>>>
>>>> I cant't have any response when I execute a query.
>>>> This problem occurs when some conditions are met.
>>>>
>>>> The conditions are below.
>>>> ------------------------------**------------------------------**
>>>> ---------
>>>> 1. Issuing "EXECUTE DIRECT" to Datanode(ofcourse, via Coordinator).
>>>>
>>>> 2. The Query Executing on Datanode has subquery on its FROM-clause.
>>>>
>>>> 3. In the subquery, it has a JOIN clause.
>>>>
>>>> 4. The Join clause is consisted with another subquery.
>>>> ------------------------------**------------------------------**
>>>> ---------
>>>>
>>>>
>>>> Simple example query is below.
>>>> ------------------------------**------------------------------**---
>>>> EXECUTE DIRECT ON (data1) $$
>>>> SELECT
>>>> count(*)
>>>> FROM
>>>> (SELECT * FROM pg_locks l LEFT JOIN
>>>> (SELECT * FROM pg_stat_activity) s ON l.database = s.datid) a
>>>> $$
>>>> ------------------------------**------------------------------**---
>>>>
>>>> FYI:
>>>> This query works fine with Postgres-XC 1.0.3.
>>>> Is this already known bug ?
>>>>
>>>>
>>>> How can I avoid this problem ?
>>>> And what kind of info do you need to investigate it ?
>>>>
>>>> ----------
>>>> NTT Software Corporation
>>>> Tomonari Katsumata
>>>>
>>>>
>>>>
>>>>
>>>> ------------------------------**------------------------------**
>>>> ------------------
>>>> How ServiceNow helps IT people transform IT departments:
>>>> 1. A cloud service to automate IT design, transition and operations
>>>> 2. Dashboards that offer high-level views of enterprise services
>>>> 3. A single system of record for all IT processes
>>>> http://p.sf.net/sfu/**servicenow-d2d-j<http://p.sf.net/sfu/servicenow-d2d-j>
>>>> ______________________________**_________________
>>>> Postgres-xc-developers mailing list
>>>> Postgres-xc-developers@lists.**sourceforge.net<Pos...@li...>
>>>> https://lists.sourceforge.net/**lists/listinfo/postgres-xc-**developers<https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers>
>>>>
>>>>
>>>
>>> ------------------------------**------------------------------**
>>> ------------------
>>> How ServiceNow helps IT people transform IT departments:
>>> 1. A cloud service to automate IT design, transition and operations
>>> 2. Dashboards that offer high-level views of enterprise services
>>> 3. A single system of record for all IT processes
>>> http://p.sf.net/sfu/**servicenow-d2d-j<http://p.sf.net/sfu/servicenow-d2d-j>
>>> ______________________________**_________________
>>> Postgres-xc-developers mailing list
>>> Postgres-xc-developers@lists.**sourceforge.net<Pos...@li...>
>>> https://lists.sourceforge.net/**lists/listinfo/postgres-xc-**developers<https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers>
>>>
>>>
>>>
>>
>
> --
> ------------------------------**--------------
> NTTソフトウェア株式会社
>   技術開発センター OSS基盤技術部門
>   勝俣 智成
> TEL：045-212-7665
> FAX：045-662-7856
> E-Mail: kat...@po....**jp<kat...@po...>
> ------------------------------**--------------
>
>
>


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

Hi Suzuki-san, Ashutosh,

 >Suzuki-san
I don't make any user tables.
As the simple example I sent before, I use only system-catalogs.

 >Ashtosh
I'm developing database monitor tool and
I use "EXECUTE DIRECT" to get database statistics data from
particular coordinator/datanode.

regard,
---------
NTT Software Corporation
Tomonari Katsumata

(2013/06/04 13:10), Ashutosh Bapat wrote:
> Hi Tomonari,
>
> Thanks for the bug report.
>
> I am curious to know, what's the purpose of using EXECUTE DIRECT? We
> discourage using Execute Direct in the applications. It's only for
> debugging purposes.
>
>
> On Tue, Jun 4, 2013 at 7:28 AM, Koichi Suzuki <koi...@gm...>wrote:
>
>> Thank you Katsumata-san for the report.
>>
>> Could you provide CREATE TABLE statement for each table involved with some
>> of the data?
>>
>> I will ad this to the bug tracker after I recreate the issue.
>>
>> Best Regards;
>>
>> ----------
>> Koichi Suzuki
>>
>>
>> 2013/6/4 Tomonari Katsumata <kat...@po...>
>>
>>> Hi, I have a problem with query executing.
>>>
>>> I cant't have any response when I execute a query.
>>> This problem occurs when some conditions are met.
>>>
>>> The conditions are below.
>>> ---------------------------------------------------------------------
>>> 1. Issuing "EXECUTE DIRECT" to Datanode(ofcourse, via Coordinator).
>>>
>>> 2. The Query Executing on Datanode has subquery on its FROM-clause.
>>>
>>> 3. In the subquery, it has a JOIN clause.
>>>
>>> 4. The Join clause is consisted with another subquery.
>>> ---------------------------------------------------------------------
>>>
>>>
>>> Simple example query is below.
>>> ---------------------------------------------------------------
>>> EXECUTE DIRECT ON (data1) $$
>>> SELECT
>>> count(*)
>>> FROM
>>> (SELECT * FROM pg_locks l LEFT JOIN
>>> (SELECT * FROM pg_stat_activity) s ON l.database = s.datid) a
>>> $$
>>> ---------------------------------------------------------------
>>>
>>> FYI:
>>> This query works fine with Postgres-XC 1.0.3.
>>> Is this already known bug ?
>>>
>>>
>>> How can I avoid this problem ?
>>> And what kind of info do you need to investigate it ?
>>>
>>> ----------
>>> NTT Software Corporation
>>> Tomonari Katsumata
>>>
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> How ServiceNow helps IT people transform IT departments:
>>> 1. A cloud service to automate IT design, transition and operations
>>> 2. Dashboards that offer high-level views of enterprise services
>>> 3. A single system of record for all IT processes
>>> http://p.sf.net/sfu/servicenow-d2d-j
>>> _______________________________________________
>>> Postgres-xc-developers mailing list
>>> Pos...@li...
>>> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>>>
>>
>>
>> ------------------------------------------------------------------------------
>> How ServiceNow helps IT people transform IT departments:
>> 1. A cloud service to automate IT design, transition and operations
>> 2. Dashboards that offer high-level views of enterprise services
>> 3. A single system of record for all IT processes
>> http://p.sf.net/sfu/servicenow-d2d-j
>> _______________________________________________
>> Postgres-xc-developers mailing list
>> Pos...@li...
>> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>>
>>
>


-- 
--------------------------------------------
NTTソフトウェア株式会社
   技術開発センター OSS基盤技術部門
   勝俣 智成
TEL：045-212-7665
FAX：045-662-7856
E-Mail: kat...@po...
--------------------------------------------

Hi Tomonari,

Thanks for the bug report.

I am curious to know, what's the purpose of using EXECUTE DIRECT? We
discourage using Execute Direct in the applications. It's only for
debugging purposes.


On Tue, Jun 4, 2013 at 7:28 AM, Koichi Suzuki <koi...@gm...>wrote:

> Thank you Katsumata-san for the report.
>
> Could you provide CREATE TABLE statement for each table involved with some
> of the data?
>
> I will ad this to the bug tracker after I recreate the issue.
>
> Best Regards;
>
> ----------
> Koichi Suzuki
>
>
> 2013/6/4 Tomonari Katsumata <kat...@po...>
>
>> Hi, I have a problem with query executing.
>>
>> I cant't have any response when I execute a query.
>> This problem occurs when some conditions are met.
>>
>> The conditions are below.
>> ---------------------------------------------------------------------
>> 1. Issuing "EXECUTE DIRECT" to Datanode(ofcourse, via Coordinator).
>>
>> 2. The Query Executing on Datanode has subquery on its FROM-clause.
>>
>> 3. In the subquery, it has a JOIN clause.
>>
>> 4. The Join clause is consisted with another subquery.
>> ---------------------------------------------------------------------
>>
>>
>> Simple example query is below.
>> ---------------------------------------------------------------
>> EXECUTE DIRECT ON (data1) $$
>> SELECT
>> count(*)
>> FROM
>> (SELECT * FROM pg_locks l LEFT JOIN
>> (SELECT * FROM pg_stat_activity) s ON l.database = s.datid) a
>> $$
>> ---------------------------------------------------------------
>>
>> FYI:
>> This query works fine with Postgres-XC 1.0.3.
>> Is this already known bug ?
>>
>>
>> How can I avoid this problem ?
>> And what kind of info do you need to investigate it ?
>>
>> ----------
>> NTT Software Corporation
>> Tomonari Katsumata
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> How ServiceNow helps IT people transform IT departments:
>> 1. A cloud service to automate IT design, transition and operations
>> 2. Dashboards that offer high-level views of enterprise services
>> 3. A single system of record for all IT processes
>> http://p.sf.net/sfu/servicenow-d2d-j
>> _______________________________________________
>> Postgres-xc-developers mailing list
>> Pos...@li...
>> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>>
>
>
>
> ------------------------------------------------------------------------------
> How ServiceNow helps IT people transform IT departments:
> 1. A cloud service to automate IT design, transition and operations
> 2. Dashboards that offer high-level views of enterprise services
> 3. A single system of record for all IT processes
> http://p.sf.net/sfu/servicenow-d2d-j
> _______________________________________________
> 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

Thank you Katsumata-san for the report.

Could you provide CREATE TABLE statement for each table involved with some
of the data?

I will ad this to the bug tracker after I recreate the issue.

Best Regards;

----------
Koichi Suzuki


2013/6/4 Tomonari Katsumata <kat...@po...>

> Hi, I have a problem with query executing.
>
> I cant't have any response when I execute a query.
> This problem occurs when some conditions are met.
>
> The conditions are below.
> ---------------------------------------------------------------------
> 1. Issuing "EXECUTE DIRECT" to Datanode(ofcourse, via Coordinator).
>
> 2. The Query Executing on Datanode has subquery on its FROM-clause.
>
> 3. In the subquery, it has a JOIN clause.
>
> 4. The Join clause is consisted with another subquery.
> ---------------------------------------------------------------------
>
>
> Simple example query is below.
> ---------------------------------------------------------------
> EXECUTE DIRECT ON (data1) $$
> SELECT
> count(*)
> FROM
> (SELECT * FROM pg_locks l LEFT JOIN
> (SELECT * FROM pg_stat_activity) s ON l.database = s.datid) a
> $$
> ---------------------------------------------------------------
>
> FYI:
> This query works fine with Postgres-XC 1.0.3.
> Is this already known bug ?
>
>
> How can I avoid this problem ?
> And what kind of info do you need to investigate it ?
>
> ----------
> NTT Software Corporation
> Tomonari Katsumata
>
>
>
>
> ------------------------------------------------------------------------------
> How ServiceNow helps IT people transform IT departments:
> 1. A cloud service to automate IT design, transition and operations
> 2. Dashboards that offer high-level views of enterprise services
> 3. A single system of record for all IT processes
> http://p.sf.net/sfu/servicenow-d2d-j
> _______________________________________________
> Postgres-xc-developers mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>

Hi, I have a problem with query executing.

I cant't have any response when I execute a query.
This problem occurs when some conditions are met.

The conditions are below.
---------------------------------------------------------------------
1. Issuing "EXECUTE DIRECT" to Datanode(ofcourse, via Coordinator).

2. The Query Executing on Datanode has subquery on its FROM-clause.

3. In the subquery, it has a JOIN clause.

4. The Join clause is consisted with another subquery.
---------------------------------------------------------------------


Simple example query is below.
---------------------------------------------------------------
EXECUTE DIRECT ON (data1) $$
SELECT
count(*)
FROM
(SELECT * FROM pg_locks l LEFT JOIN
(SELECT * FROM pg_stat_activity) s ON l.database = s.datid) a
$$
---------------------------------------------------------------

FYI:
This query works fine with Postgres-XC 1.0.3.
Is this already known bug ?


How can I avoid this problem ?
And what kind of info do you need to investigate it ?

----------
NTT Software Corporation
Tomonari Katsumata

Thanks a lot.   Another fix is welcome.
---
Koichi Suzuki



On 2013/06/03, at 17:49, Tomonari Katsumata <kat...@po...> wrote:

> Hi,
> 
> I'm testing with pgxc_ctl utility.
> This is very helpful tool,
> but I noticed two things to fix.
> 
> 1. gtm_proxy.conf written by pgxc_ctl is unavailable.
> 
> Because the value of gtm_host parameter is not quoted.
> 
> 2. misspelled message when deploying.
> 
> Not "deplloying", it's "deploying".
> 
> 
> I attached a patch against master(*)
> (*)5c07b4ec0623dfb78c7472ae28112bd8a84c5c0d
> 
> regards,
> --------------
> NTT Software Corporation
> Tomonari Katsumata
> 
> <pgxc_ctl_small_fix.patch>------------------------------------------------------------------------------
> 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

Hi,

I'm testing with pgxc_ctl utility.
This is very helpful tool,
but I noticed two things to fix.

1. gtm_proxy.conf written by pgxc_ctl is unavailable.

Because the value of gtm_host parameter is not quoted.

2. misspelled message when deploying.

Not "deplloying", it's "deploying".


I attached a patch against master(*)
(*)5c07b4ec0623dfb78c7472ae28112bd8a84c5c0d

regards,
--------------
NTT Software Corporation
Tomonari Katsumata

On Mon, Jun 3, 2013 at 10:51 AM, Abbas Butt <abb...@en...>wrote:

>
>
> On Mon, Jun 3, 2013 at 8:43 AM, Ashutosh Bapat <
> ash...@en...> wrote:
>
>>
>>
>>
>> On Mon, Jun 3, 2013 at 7:40 AM, Abbas Butt <abb...@en...>wrote:
>>
>>> Attached please find updated patch to fix the bug. The patch takes care
>>> of the bug and the regression issues resulting from the changes done in the
>>> patch. Please note that the issue in test case plancache still stands
>>> unsolved because of the following test case (simplified but taken from
>>> plancache.sql)
>>>
>>> create schema s1 create table abc (f1 int);
>>> create schema s2 create table abc (f1 int);
>>>
>>>
>>> insert into s1.abc values(123);
>>> insert into s2.abc values(456);
>>>
>>> set search_path = s1;
>>>
>>> prepare p1 as select f1 from abc;
>>> execute p1; -- works fine, results in 123
>>>
>>> set search_path = s2;
>>> execute p1; -- works fine after the patch, results in 123
>>>
>>> alter table s1.abc add column f2 float8;   -- force replan
>>> execute p1; -- fails
>>>
>>>
>> Huh! The beast bit us.
>>
>> I think the right solution here is either of two
>> 1. Take your previous patch to always use qualified names (but you need
>> to improve it not to affect the view dumps)
>> 2. Prepare the statements at the datanode at the time of prepare.
>>
>>
>> Is this test added new in 9.2?
>>
>
> No, it was added by commit 547b6e537aa8bbae83a8a4c4d0d7f216390bdb9c in
> March 2007.
>
>
>> Why didn't we see this issue the first time prepare was implemented? I
>> don't remember (but it was two years back).
>>
>
> I was unable to locate the exact reason but since statements were not
> being prepared on datanodes due to a merge issue this issue just surfaced
> up.
>
>

Well, even though statements were not getting prepared (actually prepared
statements were not being used again and again) on datanodes, we never
prepared them on datanode at the time of preparing the statement. So, this
bug should have shown itself long back.


>
>>
>>> The last execute should result in 123, whereas it results in 456. The
>>> reason is that the search path has already been changed at the datanode and
>>> a replan would mean select from abc in s2.
>>>
>>>
>>>
>>>
>>> On Tue, May 28, 2013 at 7:17 PM, Ashutosh Bapat <
>>> ash...@en...> wrote:
>>>
>>>> Hi Abbas,
>>>> I think the fix is on the right track. There are couple of improvements
>>>> that we need to do here (but you may not do those if the time doesn't
>>>> permit).
>>>>
>>>> 1. We should have a status in RemoteQuery node, as to whether the query
>>>> in the node should use extended protocol or not, rather than relying on the
>>>> presence of statement name and parameters etc. Amit has already added a
>>>> status with that effect. We need to leverage it.
>>>>
>>>>
>>>> On Tue, May 28, 2013 at 9:04 AM, Abbas Butt <
>>>> abb...@en...> wrote:
>>>>
>>>>> The patch fixes the dead code issue, that I described earlier. The
>>>>> code was dead because of two issues:
>>>>>
>>>>> 1. The function CompleteCachedPlan was wrongly setting stmt_name to
>>>>> NULL and this was the main reason ActivateDatanodeStatementOnNode was not
>>>>> being called in the function pgxc_start_command_on_connection.
>>>>> 2. The function SetRemoteStatementName was wrongly assuming that a
>>>>> prepared statement must have some parameters.
>>>>>
>>>>> Fixing these two issues makes sure that the function
>>>>> ActivateDatanodeStatementOnNode is now called and statements get prepared
>>>>> on the datanode.
>>>>> This patch would fix bug 3607975. It would however not fix the test
>>>>> case I described in my previous email because of reasons I described.
>>>>>
>>>>>
>>>>> On Tue, May 28, 2013 at 5:50 PM, Ashutosh Bapat <
>>>>> ash...@en...> wrote:
>>>>>
>>>>>> Can you please explain what this fix does? It would help to have an
>>>>>> elaborate explanation with code snippets.
>>>>>>
>>>>>>
>>>>>> On Sun, May 26, 2013 at 10:18 PM, Abbas Butt <
>>>>>> abb...@en...> wrote:
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Fri, May 24, 2013 at 7:04 PM, Ashutosh Bapat <
>>>>>>> ash...@en...> wrote:
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Fri, May 24, 2013 at 9:01 AM, Abbas Butt <
>>>>>>>> abb...@en...> wrote:
>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Fri, May 24, 2013 at 7:22 AM, Ashutosh Bapat <
>>>>>>>>> ash...@en...> wrote:
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Thu, May 23, 2013 at 9:21 PM, Abbas Butt <
>>>>>>>>>> abb...@en...> wrote:
>>>>>>>>>>
>>>>>>>>>>> Hi,
>>>>>>>>>>>
>>>>>>>>>>> While working on test case plancache it was brought up as a
>>>>>>>>>>> review comment that solving bug id 3607975 should solve the problem of the
>>>>>>>>>>> test case.
>>>>>>>>>>> However there is some confusion in the statement of bug id
>>>>>>>>>>> 3607975.
>>>>>>>>>>>
>>>>>>>>>>> "When a user does and PREPARE and then EXECUTEs multiple times,
>>>>>>>>>>> the coordinator keeps on preparing and executing the query on datanode al
>>>>>>>>>>> times, as against preparing once and executing multiple times. This is
>>>>>>>>>>> because somehow the remote query is being prepared as an unnamed statement."
>>>>>>>>>>>
>>>>>>>>>>> Consider this test case
>>>>>>>>>>>
>>>>>>>>>>> A. create table abc(a int, b int);
>>>>>>>>>>> B. insert into abc values(11, 22);
>>>>>>>>>>> C. prepare p1 as select * from abc;
>>>>>>>>>>> D. execute p1;
>>>>>>>>>>> E. execute p1;
>>>>>>>>>>> F. execute p1;
>>>>>>>>>>>
>>>>>>>>>>> Here are the confusions
>>>>>>>>>>>
>>>>>>>>>>> 1. The coordinator never prepares on datanode in response to a
>>>>>>>>>>> prepare issued by a user.
>>>>>>>>>>>      In fact step C does nothing on the datanodes.
>>>>>>>>>>>      Step D simply sends "SELECT a, b FROM abc" to all datanodes.
>>>>>>>>>>>
>>>>>>>>>>> 2. In step D, ExecuteQuery calls BuildCachedPlan to build a new
>>>>>>>>>>> generic plan,
>>>>>>>>>>>     and steps E and F use the already built generic plan.
>>>>>>>>>>>     For details see function GetCachedPlan.
>>>>>>>>>>>     This means that executing a prepared statement again and
>>>>>>>>>>> again does use cached plans
>>>>>>>>>>>     and does not prepare again and again every time we issue an
>>>>>>>>>>> execute.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>> The problem is not here. The problem is in do_query() where
>>>>>>>>>> somehow the name of prepared statement gets wiped out and we keep on
>>>>>>>>>> preparing unnamed statements at the datanode.
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> We never prepare any named/unnamed statements on the datanode. I
>>>>>>>>> spent time looking at the code written in do_query and functions called
>>>>>>>>> from with in do_query to handle prepared statements but the code written in
>>>>>>>>> pgxc_start_command_on_connection to handle statements prepared on datanodes
>>>>>>>>> is dead as of now. It is never called during the complete regression run.
>>>>>>>>> The function ActivateDatanodeStatementOnNode is never called. The way
>>>>>>>>> prepared statements are being handled now is the same as I described
>>>>>>>>> earlier in the mail chain with the help of an example.
>>>>>>>>> The code that is dead was originally added by Mason through commit
>>>>>>>>> d6d2d3d925f571b0b58ff6b4f6504d88e96bb342, back in December 2010. This code
>>>>>>>>> has been changed a lot over the last two years. This commit does not
>>>>>>>>> contain any test cases so I am not sure how did it use to work back then.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>> This code wasn't dead, when I worked on prepared statements. So,
>>>>>>>> something has gone wrong in-between. That's what we need to find out and
>>>>>>>> fix. Not preparing statements on the datanode is not good for performance
>>>>>>>> either.
>>>>>>>>
>>>>>>>
>>>>>>> I was able to find the reason why the code was dead and the attached
>>>>>>> patch (WIP) fixes the problem. This would now ensure that statements are
>>>>>>> prepared on datanodes whenever required. However there is a problem in the
>>>>>>> way prepared statements are handled. The problem is that unless a prepared
>>>>>>> statement is executed it is never prepared on datanodes, hence changing the
>>>>>>> path before executing the statement gives us incorrect results. For Example
>>>>>>>
>>>>>>>   create schema s1 create table abc (f1 int) distribute by
>>>>>>> replication;
>>>>>>>   create schema s2 create table abc (f1 int) distribute by
>>>>>>> replication;
>>>>>>>
>>>>>>>   insert into s1.abc values(123);
>>>>>>>   insert into s2.abc values(456);
>>>>>>>   set search_path = s2;
>>>>>>>   prepare p1 as select f1 from abc;
>>>>>>>   set search_path = s1;
>>>>>>>   execute p1;
>>>>>>>
>>>>>>> The last execute results in 123, where as it should have resulted in
>>>>>>> 456.
>>>>>>> I can finalize the attached patch by fixing any regression issues
>>>>>>> that may result and that would fix 3607975 and improve performance however
>>>>>>> the above test case would still fail.
>>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> My conclusion is that the bug ID 3607975 is not reproducible.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>> Did you verify it under the debugger? If that would have been the
>>>>>>>>>> case, we would not have seen this problem if search_path changed in between
>>>>>>>>>> steps D and E.
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> If search path is changed between steps D & E, the problem occurs
>>>>>>>>> because when the remote query node is created, schema qualification is not
>>>>>>>>> added in the sql statement to be sent to the datanode, but changes in
>>>>>>>>> search path do get communicated to the datanode. The sql statement is built
>>>>>>>>> when execute is issued for the first time and is reused on subsequent
>>>>>>>>> executes. The datanode is totally unaware that the select that it just
>>>>>>>>> received is due to an execute of a prepared statement that was prepared
>>>>>>>>> when search path was some thing else.
>>>>>>>>>
>>>>>>>>>
>>>>>>>> Fixing the prepared statements the way I suggested, would fix the
>>>>>>>> problem, since the statement will get prepared at the datanode, with the
>>>>>>>> same search path settings, as it would on the coordinator.
>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>  Comments are welcome.
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> *Abbas*
>>>>>>>>>>>  Architect
>>>>>>>>>>>
>>>>>>>>>>> Ph: 92.334.5100153
>>>>>>>>>>>  Skype ID: gabbasb
>>>>>>>>>>> www.enterprisedb.co <http://www.enterprisedb.com/>m<http://www.enterprisedb.com/>
>>>>>>>>>>> *
>>>>>>>>>>> Follow us on Twitter*
>>>>>>>>>>> @EnterpriseDB
>>>>>>>>>>>
>>>>>>>>>>> Visit EnterpriseDB for tutorials, webinars, whitepapers<http://www.enterprisedb.com/resources-community>and more<http://www.enterprisedb.com/resources-community>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> ------------------------------------------------------------------------------
>>>>>>>>>>> Try New Relic Now & We'll Send You this Cool Shirt
>>>>>>>>>>> New Relic is the only SaaS-based application performance
>>>>>>>>>>> monitoring service
>>>>>>>>>>> that delivers powerful full stack analytics. Optimize and
>>>>>>>>>>> monitor your
>>>>>>>>>>> browser, app, & servers with just a few lines of code. Try New
>>>>>>>>>>> Relic
>>>>>>>>>>> and get this awesome Nerd Life shirt!
>>>>>>>>>>> http://p.sf.net/sfu/newrelic_d2d_may
>>>>>>>>>>> _______________________________________________
>>>>>>>>>>> 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
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> --
>>>>>>>>> *Abbas*
>>>>>>>>>  Architect
>>>>>>>>>
>>>>>>>>> Ph: 92.334.5100153
>>>>>>>>>  Skype ID: gabbasb
>>>>>>>>> www.enterprisedb.co <http://www.enterprisedb.com/>m<http://www.enterprisedb.com/>
>>>>>>>>> *
>>>>>>>>> Follow us on Twitter*
>>>>>>>>> @EnterpriseDB
>>>>>>>>>
>>>>>>>>> Visit EnterpriseDB for tutorials, webinars, whitepapers<http://www.enterprisedb.com/resources-community>and more<http://www.enterprisedb.com/resources-community>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Best Wishes,
>>>>>>>> Ashutosh Bapat
>>>>>>>> EntepriseDB Corporation
>>>>>>>> The Postgres Database Company
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> --
>>>>>>> *Abbas*
>>>>>>>  Architect
>>>>>>>
>>>>>>> Ph: 92.334.5100153
>>>>>>>  Skype ID: gabbasb
>>>>>>> www.enterprisedb.co <http://www.enterprisedb.com/>m<http://www.enterprisedb.com/>
>>>>>>> *
>>>>>>> Follow us on Twitter*
>>>>>>> @EnterpriseDB
>>>>>>>
>>>>>>> Visit EnterpriseDB for tutorials, webinars, whitepapers<http://www.enterprisedb.com/resources-community>and more<http://www.enterprisedb.com/resources-community>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Best Wishes,
>>>>>> Ashutosh Bapat
>>>>>> EntepriseDB Corporation
>>>>>> The Postgres Database Company
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> --
>>>>> *Abbas*
>>>>>  Architect
>>>>>
>>>>> Ph: 92.334.5100153
>>>>>  Skype ID: gabbasb
>>>>> www.enterprisedb.co <http://www.enterprisedb.com/>m<http://www.enterprisedb.com/>
>>>>> *
>>>>> Follow us on Twitter*
>>>>> @EnterpriseDB
>>>>>
>>>>> Visit EnterpriseDB for tutorials, webinars, whitepapers<http://www.enterprisedb.com/resources-community>and more<http://www.enterprisedb.com/resources-community>
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Best Wishes,
>>>> Ashutosh Bapat
>>>> EntepriseDB Corporation
>>>> The Postgres Database Company
>>>>
>>>
>>>
>>>
>>> --
>>> --
>>> *Abbas*
>>>  Architect
>>>
>>> Ph: 92.334.5100153
>>>  Skype ID: gabbasb
>>> www.enterprisedb.co <http://www.enterprisedb.com/>m<http://www.enterprisedb.com/>
>>> *
>>> Follow us on Twitter*
>>> @EnterpriseDB
>>>
>>> Visit EnterpriseDB for tutorials, webinars, whitepapers<http://www.enterprisedb.com/resources-community>and more<http://www.enterprisedb.com/resources-community>
>>>
>>
>>
>>
>> --
>> Best Wishes,
>> Ashutosh Bapat
>> EntepriseDB Corporation
>> The Postgres Database Company
>>
>
>
>
> --
> --
> *Abbas*
>  Architect
>
> Ph: 92.334.5100153
>  Skype ID: gabbasb
> www.enterprisedb.co <http://www.enterprisedb.com/>m<http://www.enterprisedb.com/>
> *
> Follow us on Twitter*
> @EnterpriseDB
>
> Visit EnterpriseDB for tutorials, webinars, whitepapers<http://www.enterprisedb.com/resources-community>and more<http://www.enterprisedb.com/resources-community>
>



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

Abbas,
Can you please check-in this patch after making sure that it doesn't cause
any additional regression failures.


On Mon, Jun 3, 2013 at 5:59 AM, Abbas Butt <abb...@en...>wrote:

> Hi,
> Attached please find a revised patch that removes the variable non_fqs_dml
> from RemoteQueryState whihc is no longer needed.
> With this small change included the patch is good to go.
>
>
>
> On Thu, May 23, 2013 at 9:41 AM, Abbas Butt <abb...@en...>wrote:
>
>> I will try to spare some time for this over the weekend.
>>
>>
>> On Thu, May 23, 2013 at 1:09 AM, Ahsan Hadi <ahs...@en...>wrote:
>>
>>> Abbas,
>>> Can you please review this patch this week?
>>>
>>>
>>> On Tue, May 21, 2013 at 3:55 AM, Amit Khandekar <
>>> ami...@en...> wrote:
>>>
>>>> Currently the number of tuples processed is updated in both
>>>> HandleCommandComplete and ExecInsert/Update/Delete.
>>>>
>>>> In HandleCommandComplete() it gets it from the command tag returned
>>>> from the datanode i.e. INSERT 0 2, UPDATE 5 and likewise. And then it
>>>> updates estate->es_processed. But it does this only for FQS. For non-FQS,
>>>> in ExecInsert/Update,  it is just incremented by 1. So if a trigger
>>>> function skips one row on datanode, the command tag returned from datanode
>>>> is INSERT 0 0. But still in ExecInsert() increments the row count.
>>>>
>>>> I have added a new field RemoteQueryState->rqs_processed, which is
>>>> updated in HandleCommandComplete(). Then it is used in
>>>> ExecInsert/Update/Delete() for non-FQS, and in RemoteQueryNext() for FQS.
>>>>
>>>> While fixing this issue, I see that there seem to be some issue with
>>>> combiner->command_complete_count. Currently it checks for consistency of
>>>> number of tuples returned for replicated tables, but it does that only for
>>>> FQS. Need to completely remove the dependency on whether it's an FQS or
>>>> non-FQS DML query. For this, command_complete_count needs to be better
>>>> handled. I felt it needs some refactoring which I did not feel good to do
>>>> in this release. Currently this field is being updated for each iteration
>>>> of FetchTuple by re-using the same combiner for each iteration, whereas it
>>>> seems it should be updated only for each node execution, not for each tuple
>>>> fetched. I haven't touched this part, but added a TODO, and opened 3613645.
>>>>
>>>> Added some testcases in existing tests xc_trigship and xc_returning.
>>>>
>>>>
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Try New Relic Now & We'll Send You this Cool Shirt
>>>> New Relic is the only SaaS-based application performance monitoring
>>>> service
>>>> that delivers powerful full stack analytics. Optimize and monitor your
>>>> browser, app, & servers with just a few lines of code. Try New Relic
>>>> and get this awesome Nerd Life shirt!
>>>> http://p.sf.net/sfu/newrelic_d2d_may
>>>> _______________________________________________
>>>> Postgres-xc-developers mailing list
>>>> Pos...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>>>>
>>>>
>>>
>>>
>>> --
>>> Ahsan Hadi
>>> Snr Director Product Development
>>> EnterpriseDB Corporation
>>> The Enterprise Postgres Company
>>>
>>> Phone: +92-51-8358874
>>> Mobile: +92-333-5162114
>>>
>>> Website: www.enterprisedb.com
>>> EnterpriseDB Blog: http://blogs.enterprisedb.com/
>>> Follow us on Twitter: http://www.twitter.com/enterprisedb
>>>
>>> This e-mail message (and any attachment) is intended for the use of the
>>> individual or entity to whom it is addressed. This message contains
>>> information from EnterpriseDB Corporation that may be privileged,
>>> confidential, or exempt from disclosure under applicable law. If you are
>>> not the intended recipient or authorized to receive this for the intended
>>> recipient, any use, dissemination, distribution, retention, archiving, or
>>> copying of this communication is strictly prohibited. If you have received
>>> this e-mail in error, please notify the sender immediately by reply e-mail
>>> and delete this message.
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Try New Relic Now & We'll Send You this Cool Shirt
>>> New Relic is the only SaaS-based application performance monitoring
>>> service
>>> that delivers powerful full stack analytics. Optimize and monitor your
>>> browser, app, & servers with just a few lines of code. Try New Relic
>>> and get this awesome Nerd Life shirt!
>>> http://p.sf.net/sfu/newrelic_d2d_may
>>> _______________________________________________
>>> Postgres-xc-developers mailing list
>>> Pos...@li...
>>> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>>>
>>>
>>
>>
>> --
>> --
>> *Abbas*
>>  Architect
>>
>> Ph: 92.334.5100153
>>  Skype ID: gabbasb
>> www.enterprisedb.co <http://www.enterprisedb.com/>m<http://www.enterprisedb.com/>
>> *
>> Follow us on Twitter*
>> @EnterpriseDB
>>
>> Visit EnterpriseDB for tutorials, webinars, whitepapers<http://www.enterprisedb.com/resources-community>and more<http://www.enterprisedb.com/resources-community>
>>
>
>
>
> --
> --
> *Abbas*
>  Architect
>
> Ph: 92.334.5100153
>  Skype ID: gabbasb
> www.enterprisedb.co <http://www.enterprisedb.com/>m<http://www.enterprisedb.com/>
> *
> Follow us on Twitter*
> @EnterpriseDB
>
> Visit EnterpriseDB for tutorials, webinars, whitepapers<http://www.enterprisedb.com/resources-community>and more<http://www.enterprisedb.com/resources-community>
>



-- 
Ahsan Hadi
Snr Director Product Development
EnterpriseDB Corporation
The Enterprise Postgres Company

Phone: +92-51-8358874
Mobile: +92-333-5162114

Website: www.enterprisedb.com
EnterpriseDB Blog: http://blogs.enterprisedb.com/
Follow us on Twitter: http://www.twitter.com/enterprisedb

This e-mail message (and any attachment) is intended for the use of the
individual or entity to whom it is addressed. This message contains
information from EnterpriseDB Corporation that may be privileged,
confidential, or exempt from disclosure under applicable law. If you are
not the intended recipient or authorized to receive this for the intended
recipient, any use, dissemination, distribution, retention, archiving, or
copying of this communication is strictly prohibited. If you have received
this e-mail in error, please notify the sender immediately by reply e-mail
and delete this message.

Sorry, I forgot to send to developers ML.
---
Koichi Suzuki



Begin forwarded message:

> 差出人: Koichi Suzuki <koi...@gm...>
> 件名: [Postgres-xc-core] Patch to backup restart port for barrier
> 日時: 2013年6月3日 14:30:17 JST
> 宛先: Postgres-XC core <Pos...@li...>
> 
> PFA the patch to backup gtm restart point for each CREATE BARRIER command.    This is needed to make stable restoration point by PITR.
> 
> ----------
> Koichi Suzuki
> ------------------------------------------------------------------------------
> 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-core mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-core

On Mon, Jun 3, 2013 at 8:43 AM, Ashutosh Bapat <
ash...@en...> wrote:

>
>
>
> On Mon, Jun 3, 2013 at 7:40 AM, Abbas Butt <abb...@en...>wrote:
>
>> Attached please find updated patch to fix the bug. The patch takes care
>> of the bug and the regression issues resulting from the changes done in the
>> patch. Please note that the issue in test case plancache still stands
>> unsolved because of the following test case (simplified but taken from
>> plancache.sql)
>>
>> create schema s1 create table abc (f1 int);
>> create schema s2 create table abc (f1 int);
>>
>>
>> insert into s1.abc values(123);
>> insert into s2.abc values(456);
>>
>> set search_path = s1;
>>
>> prepare p1 as select f1 from abc;
>> execute p1; -- works fine, results in 123
>>
>> set search_path = s2;
>> execute p1; -- works fine after the patch, results in 123
>>
>> alter table s1.abc add column f2 float8;   -- force replan
>> execute p1; -- fails
>>
>>
> Huh! The beast bit us.
>
> I think the right solution here is either of two
> 1. Take your previous patch to always use qualified names (but you need to
> improve it not to affect the view dumps)
> 2. Prepare the statements at the datanode at the time of prepare.
>
>
> Is this test added new in 9.2?
>

No, it was added by commit 547b6e537aa8bbae83a8a4c4d0d7f216390bdb9c in
March 2007.


> Why didn't we see this issue the first time prepare was implemented? I
> don't remember (but it was two years back).
>

I was unable to locate the exact reason but since statements were not being
prepared on datanodes due to a merge issue this issue just surfaced up.


>
>
>> The last execute should result in 123, whereas it results in 456. The
>> reason is that the search path has already been changed at the datanode and
>> a replan would mean select from abc in s2.
>>
>>
>>
>>
>> On Tue, May 28, 2013 at 7:17 PM, Ashutosh Bapat <
>> ash...@en...> wrote:
>>
>>> Hi Abbas,
>>> I think the fix is on the right track. There are couple of improvements
>>> that we need to do here (but you may not do those if the time doesn't
>>> permit).
>>>
>>> 1. We should have a status in RemoteQuery node, as to whether the query
>>> in the node should use extended protocol or not, rather than relying on the
>>> presence of statement name and parameters etc. Amit has already added a
>>> status with that effect. We need to leverage it.
>>>
>>>
>>> On Tue, May 28, 2013 at 9:04 AM, Abbas Butt <abb...@en...
>>> > wrote:
>>>
>>>> The patch fixes the dead code issue, that I described earlier. The code
>>>> was dead because of two issues:
>>>>
>>>> 1. The function CompleteCachedPlan was wrongly setting stmt_name to
>>>> NULL and this was the main reason ActivateDatanodeStatementOnNode was not
>>>> being called in the function pgxc_start_command_on_connection.
>>>> 2. The function SetRemoteStatementName was wrongly assuming that a
>>>> prepared statement must have some parameters.
>>>>
>>>> Fixing these two issues makes sure that the function
>>>> ActivateDatanodeStatementOnNode is now called and statements get prepared
>>>> on the datanode.
>>>> This patch would fix bug 3607975. It would however not fix the test
>>>> case I described in my previous email because of reasons I described.
>>>>
>>>>
>>>> On Tue, May 28, 2013 at 5:50 PM, Ashutosh Bapat <
>>>> ash...@en...> wrote:
>>>>
>>>>> Can you please explain what this fix does? It would help to have an
>>>>> elaborate explanation with code snippets.
>>>>>
>>>>>
>>>>> On Sun, May 26, 2013 at 10:18 PM, Abbas Butt <
>>>>> abb...@en...> wrote:
>>>>>
>>>>>>
>>>>>>
>>>>>> On Fri, May 24, 2013 at 7:04 PM, Ashutosh Bapat <
>>>>>> ash...@en...> wrote:
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Fri, May 24, 2013 at 9:01 AM, Abbas Butt <
>>>>>>> abb...@en...> wrote:
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Fri, May 24, 2013 at 7:22 AM, Ashutosh Bapat <
>>>>>>>> ash...@en...> wrote:
>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Thu, May 23, 2013 at 9:21 PM, Abbas Butt <
>>>>>>>>> abb...@en...> wrote:
>>>>>>>>>
>>>>>>>>>> Hi,
>>>>>>>>>>
>>>>>>>>>> While working on test case plancache it was brought up as a
>>>>>>>>>> review comment that solving bug id 3607975 should solve the problem of the
>>>>>>>>>> test case.
>>>>>>>>>> However there is some confusion in the statement of bug id
>>>>>>>>>> 3607975.
>>>>>>>>>>
>>>>>>>>>> "When a user does and PREPARE and then EXECUTEs multiple times,
>>>>>>>>>> the coordinator keeps on preparing and executing the query on datanode al
>>>>>>>>>> times, as against preparing once and executing multiple times. This is
>>>>>>>>>> because somehow the remote query is being prepared as an unnamed statement."
>>>>>>>>>>
>>>>>>>>>> Consider this test case
>>>>>>>>>>
>>>>>>>>>> A. create table abc(a int, b int);
>>>>>>>>>> B. insert into abc values(11, 22);
>>>>>>>>>> C. prepare p1 as select * from abc;
>>>>>>>>>> D. execute p1;
>>>>>>>>>> E. execute p1;
>>>>>>>>>> F. execute p1;
>>>>>>>>>>
>>>>>>>>>> Here are the confusions
>>>>>>>>>>
>>>>>>>>>> 1. The coordinator never prepares on datanode in response to a
>>>>>>>>>> prepare issued by a user.
>>>>>>>>>>      In fact step C does nothing on the datanodes.
>>>>>>>>>>      Step D simply sends "SELECT a, b FROM abc" to all datanodes.
>>>>>>>>>>
>>>>>>>>>> 2. In step D, ExecuteQuery calls BuildCachedPlan to build a new
>>>>>>>>>> generic plan,
>>>>>>>>>>     and steps E and F use the already built generic plan.
>>>>>>>>>>     For details see function GetCachedPlan.
>>>>>>>>>>     This means that executing a prepared statement again and
>>>>>>>>>> again does use cached plans
>>>>>>>>>>     and does not prepare again and again every time we issue an
>>>>>>>>>> execute.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>> The problem is not here. The problem is in do_query() where
>>>>>>>>> somehow the name of prepared statement gets wiped out and we keep on
>>>>>>>>> preparing unnamed statements at the datanode.
>>>>>>>>>
>>>>>>>>
>>>>>>>> We never prepare any named/unnamed statements on the datanode. I
>>>>>>>> spent time looking at the code written in do_query and functions called
>>>>>>>> from with in do_query to handle prepared statements but the code written in
>>>>>>>> pgxc_start_command_on_connection to handle statements prepared on datanodes
>>>>>>>> is dead as of now. It is never called during the complete regression run.
>>>>>>>> The function ActivateDatanodeStatementOnNode is never called. The way
>>>>>>>> prepared statements are being handled now is the same as I described
>>>>>>>> earlier in the mail chain with the help of an example.
>>>>>>>> The code that is dead was originally added by Mason through commit
>>>>>>>> d6d2d3d925f571b0b58ff6b4f6504d88e96bb342, back in December 2010. This code
>>>>>>>> has been changed a lot over the last two years. This commit does not
>>>>>>>> contain any test cases so I am not sure how did it use to work back then.
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> This code wasn't dead, when I worked on prepared statements. So,
>>>>>>> something has gone wrong in-between. That's what we need to find out and
>>>>>>> fix. Not preparing statements on the datanode is not good for performance
>>>>>>> either.
>>>>>>>
>>>>>>
>>>>>> I was able to find the reason why the code was dead and the attached
>>>>>> patch (WIP) fixes the problem. This would now ensure that statements are
>>>>>> prepared on datanodes whenever required. However there is a problem in the
>>>>>> way prepared statements are handled. The problem is that unless a prepared
>>>>>> statement is executed it is never prepared on datanodes, hence changing the
>>>>>> path before executing the statement gives us incorrect results. For Example
>>>>>>
>>>>>>   create schema s1 create table abc (f1 int) distribute by
>>>>>> replication;
>>>>>>   create schema s2 create table abc (f1 int) distribute by
>>>>>> replication;
>>>>>>
>>>>>>   insert into s1.abc values(123);
>>>>>>   insert into s2.abc values(456);
>>>>>>   set search_path = s2;
>>>>>>   prepare p1 as select f1 from abc;
>>>>>>   set search_path = s1;
>>>>>>   execute p1;
>>>>>>
>>>>>> The last execute results in 123, where as it should have resulted in
>>>>>> 456.
>>>>>> I can finalize the attached patch by fixing any regression issues
>>>>>> that may result and that would fix 3607975 and improve performance however
>>>>>> the above test case would still fail.
>>>>>>
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>>> My conclusion is that the bug ID 3607975 is not reproducible.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>> Did you verify it under the debugger? If that would have been the
>>>>>>>>> case, we would not have seen this problem if search_path changed in between
>>>>>>>>> steps D and E.
>>>>>>>>>
>>>>>>>>
>>>>>>>> If search path is changed between steps D & E, the problem occurs
>>>>>>>> because when the remote query node is created, schema qualification is not
>>>>>>>> added in the sql statement to be sent to the datanode, but changes in
>>>>>>>> search path do get communicated to the datanode. The sql statement is built
>>>>>>>> when execute is issued for the first time and is reused on subsequent
>>>>>>>> executes. The datanode is totally unaware that the select that it just
>>>>>>>> received is due to an execute of a prepared statement that was prepared
>>>>>>>> when search path was some thing else.
>>>>>>>>
>>>>>>>>
>>>>>>> Fixing the prepared statements the way I suggested, would fix the
>>>>>>> problem, since the statement will get prepared at the datanode, with the
>>>>>>> same search path settings, as it would on the coordinator.
>>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>  Comments are welcome.
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> *Abbas*
>>>>>>>>>>  Architect
>>>>>>>>>>
>>>>>>>>>> Ph: 92.334.5100153
>>>>>>>>>>  Skype ID: gabbasb
>>>>>>>>>> www.enterprisedb.co <http://www.enterprisedb.com/>m<http://www.enterprisedb.com/>
>>>>>>>>>> *
>>>>>>>>>> Follow us on Twitter*
>>>>>>>>>> @EnterpriseDB
>>>>>>>>>>
>>>>>>>>>> Visit EnterpriseDB for tutorials, webinars, whitepapers<http://www.enterprisedb.com/resources-community>and more<http://www.enterprisedb.com/resources-community>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> ------------------------------------------------------------------------------
>>>>>>>>>> Try New Relic Now & We'll Send You this Cool Shirt
>>>>>>>>>> New Relic is the only SaaS-based application performance
>>>>>>>>>> monitoring service
>>>>>>>>>> that delivers powerful full stack analytics. Optimize and monitor
>>>>>>>>>> your
>>>>>>>>>> browser, app, & servers with just a few lines of code. Try New
>>>>>>>>>> Relic
>>>>>>>>>> and get this awesome Nerd Life shirt!
>>>>>>>>>> http://p.sf.net/sfu/newrelic_d2d_may
>>>>>>>>>> _______________________________________________
>>>>>>>>>> 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
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> --
>>>>>>>> *Abbas*
>>>>>>>>  Architect
>>>>>>>>
>>>>>>>> Ph: 92.334.5100153
>>>>>>>>  Skype ID: gabbasb
>>>>>>>> www.enterprisedb.co <http://www.enterprisedb.com/>m<http://www.enterprisedb.com/>
>>>>>>>> *
>>>>>>>> Follow us on Twitter*
>>>>>>>> @EnterpriseDB
>>>>>>>>
>>>>>>>> Visit EnterpriseDB for tutorials, webinars, whitepapers<http://www.enterprisedb.com/resources-community>and more<http://www.enterprisedb.com/resources-community>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Best Wishes,
>>>>>>> Ashutosh Bapat
>>>>>>> EntepriseDB Corporation
>>>>>>> The Postgres Database Company
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> --
>>>>>> *Abbas*
>>>>>>  Architect
>>>>>>
>>>>>> Ph: 92.334.5100153
>>>>>>  Skype ID: gabbasb
>>>>>> www.enterprisedb.co <http://www.enterprisedb.com/>m<http://www.enterprisedb.com/>
>>>>>> *
>>>>>> Follow us on Twitter*
>>>>>> @EnterpriseDB
>>>>>>
>>>>>> Visit EnterpriseDB for tutorials, webinars, whitepapers<http://www.enterprisedb.com/resources-community>and more<http://www.enterprisedb.com/resources-community>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Best Wishes,
>>>>> Ashutosh Bapat
>>>>> EntepriseDB Corporation
>>>>> The Postgres Database Company
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> --
>>>> *Abbas*
>>>>  Architect
>>>>
>>>> Ph: 92.334.5100153
>>>>  Skype ID: gabbasb
>>>> www.enterprisedb.co <http://www.enterprisedb.com/>m<http://www.enterprisedb.com/>
>>>> *
>>>> Follow us on Twitter*
>>>> @EnterpriseDB
>>>>
>>>> Visit EnterpriseDB for tutorials, webinars, whitepapers<http://www.enterprisedb.com/resources-community>and more<http://www.enterprisedb.com/resources-community>
>>>>
>>>
>>>
>>>
>>> --
>>> Best Wishes,
>>> Ashutosh Bapat
>>> EntepriseDB Corporation
>>> The Postgres Database Company
>>>
>>
>>
>>
>> --
>> --
>> *Abbas*
>>  Architect
>>
>> Ph: 92.334.5100153
>>  Skype ID: gabbasb
>> www.enterprisedb.co <http://www.enterprisedb.com/>m<http://www.enterprisedb.com/>
>> *
>> Follow us on Twitter*
>> @EnterpriseDB
>>
>> Visit EnterpriseDB for tutorials, webinars, whitepapers<http://www.enterprisedb.com/resources-community>and more<http://www.enterprisedb.com/resources-community>
>>
>
>
>
> --
> Best Wishes,
> Ashutosh Bapat
> EntepriseDB Corporation
> The Postgres Database Company
>



-- 
-- 
*Abbas*
 Architect

Ph: 92.334.5100153
 Skype ID: gabbasb
www.enterprisedb.co
<http://www.enterprisedb.com/>m<http://www.enterprisedb.com/>
*
Follow us on Twitter*
@EnterpriseDB

Visit EnterpriseDB for tutorials, webinars,
whitepapers<http://www.enterprisedb.com/resources-community>and
more<http://www.enterprisedb.com/resources-community>