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

Hi,

I am newbie to this open source group and would like to contribute to Postgres-XC.
I have knowledge of PostgreSQL and basic concept of Postgres-XC but in order to contribute in terms of code, if I can get some direction like

1.       List of all latest document including architecture document,  design or any other corresponding document to understand code.

2.       Set-up related information

3.       Anything else which you feel important.

I have got few document by googling but it is better If I can get something from developers of this project.

Thanks and Regards,
Kumar Rajeev Rastogi

Thanks. This is now committed.

Thanks,
Pavan

On Wed, Jan 28, 2015 at 4:52 PM, Jaimin Pan <jai...@gm...> wrote:

> Hi All,
>
> It'a a patch for fixing bug in gtm_serialize.c
>
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming. The Go Parallel Website,
> sponsored by Intel and developed in partnership with Slashdot Media, is
> your
> hub for all things parallel software development, from weekly thought
> leadership blogs to news, videos, case studies, tutorials and more. Take a
> look and join the conversation now. http://goparallel.sourceforge.net/
> _______________________________________________
> Postgres-xl-developers mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xl-developers
>
>


-- 
Pavan Deolasee
http://www.linkedin.com/in/pavandeolasee

Thanks Jaimin. This is now committed. Sorry for the delay.

Thanks,
Pavan

On Sat, Jan 24, 2015 at 11:15 AM, Jaimin Pan <jai...@gm...> wrote:

> Hi All,
>
> The gtm.patch1 is for TXN_START_PREPARED backup process.
> The gtm.patch2 does some code refactory after apply gtm.patch1.
>
>
> ------------------------------------------------------------------------------
> New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
> GigeNET is offering a free month of service with a new server in Ashburn.
> Choose from 2 high performing configs, both with 100TB of bandwidth.
> Higher redundancy.Lower latency.Increased capacity.Completely compliant.
> http://p.sf.net/sfu/gigenet
> _______________________________________________
> Postgres-xl-developers mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xl-developers
>
>


-- 
Pavan Deolasee
http://www.linkedin.com/in/pavandeolasee

Hi All,

It'a a patch for fixing bug in gtm_serialize.c

hi 
  When I use pgxc_ctl tool to monitor datanode.  I found that pgxc_ctl monitor function have some problems as follow:
      1.If datanode is recovering, then pgxc_ctl monitor issue wrong state information that datanode is not runing. 
         Obviously, It is wrong. I hope pgxc_ctl tool tell me that datanode is recovering.
      2.If datanode is shutting down. pgxc_ctl mointor function has the same problem as above.

Now I have a design that it can provide detailed and precise information on the status of the database.
In datanode, there is a file in data folder. Name is pg_control,  Path is data/global.

This file records the current state information about the datanode as follow:
   Database cluster state:               in production
   Database cluster state:               starting up
   Database cluster state:               shut down
   Database cluster state:               shut down in recovery
   Database cluster state:               shutting down
   Database cluster state:               in crash recovery
   Database cluster state:               in archive recovery
     
Now if I know datanode master process is active. Then I can make sure that the stats information in pg_control is right.

Pseudocode as follows:
   1.See whether datanode master process is active with ssh command(ssh pgxc@192.168.198.101 ps -ef | grep  /home/pgxc/data/datanode)
   2.If master process is active, then we can get current state information with ssh command(ssh pgxc@192.168.198.101 /home/pgxc/postgres_xc/bin/pg_controldata                         /home/pgxc/data/dn_master/ | grep "Database cluster state")
   3.If master process is not active. then tell user that datanode service is shut down.

Please help to review this design, If any problem, please let me know.
Thank your for help




xu...@cm...

Hi All,

The gtm.patch1 is for TXN_START_PREPARED backup process.
The gtm.patch2 does some code refactory after apply gtm.patch1.

Hi All,

The patch is for Begin Transaction. It uses uninitialize timestamp for
backup.

Hi,

this patch reduce error level to LOG in ServerLoop() for GTM and GTM proxy.
    
Because PG_exception_stack not set in main thread, elog with
ERROR(eg. thread create failed) can cause whole program exit, see
pg_re_throw(). This patch refers to error process of postmaster,
which just log error.

Note, palloc still used in ServerLoop(), which will raise a ERROR
message if out of memory, fix it need another patch.


-- 
Best Regards,
Wang Diancheng

diff --git a/src/test/regress/expected/json_1.out b/src/test/regress/expected/json_1.out
index befe47d..04efaaa 100644
--- a/src/test/regress/expected/json_1.out
+++ b/src/test/regress/expected/json_1.out
@@ -386,7 +386,7 @@ CREATE TEMP TABLE rows AS
 SELECT x, 'txt' || x as y
 FROM generate_series(1,3) AS x;
 SELECT row_to_json(q,true)
-FROM rows q;
+FROM rows q order by x;
  row_to_json  
 --------------
  {"x":1,     +

I need closer look at the code.    Most of the lines from
configuration prototype are removed.

Regards;
---
Koichi Suzuki


2014-12-24 18:24 GMT+09:00 Jaimin Pan <jai...@gm...>:
> If configure on the other directory. pgxc_ctl can not be built correct.
> Here is the patch to fix the issue and add explicit dependency for make.
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming! The Go Parallel Website,
> sponsored by Intel and developed in partnership with Slashdot Media, is your
> hub for all things parallel software development, from weekly thought
> leadership blogs to news, videos, case studies, tutorials and more. Take a
> look and join the conversation now. http://goparallel.sourceforge.net
> _______________________________________________
> Postgres-xc-developers mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>

The patch looks nice to handle session parameters more consistently.
Please let me check the code more closely before commit.

I hope the commit can be applied to all the stable branches.

Best;
---
Koichi Suzuki


2014-12-23 23:51 GMT+09:00 Jaimin Pan <jai...@gm...>:
> Hi all,
>
> I found that the set command handled by pool is not decent. Especially, the
> memory usage will grows up with the same set.
> Here is the patch to refectory and fix the potential problem.
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming! The Go Parallel Website,
> sponsored by Intel and developed in partnership with Slashdot Media, is your
> hub for all things parallel software development, from weekly thought
> leadership blogs to news, videos, case studies, tutorials and more. Take a
> look and join the conversation now. http://goparallel.sourceforge.net
> _______________________________________________
> Postgres-xc-developers mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>

Thanks Michael.   It was what I was considering.   I agree that we
shouldn't get upstream patches before we merge them into XC.

Appreciate for your comment.
---
Koichi Suzuki


2014-12-24 8:38 GMT+09:00 Michael Paquier <mic...@gm...>:
> On Tue, Dec 23, 2014 at 1:57 PM, Jaimin Pan <jai...@gm...> wrote:
>> I check the PG repo master branch(latest commit in my view
>> d69ffd6f035fe24483247bf9b2335d7474eaf31a).
>> And there is no such error, seem no modified ever.
> I disagree, per se this commit in Postgres:
> commit: 5242fefb471d1fb2d0f35a33bde3570e19acd4b1
> author: Tom Lane <tg...@ss...>
> date: Sat, 15 Jun 2013 14:11:43 -0400
> Be consistent about #define'ing configure symbols as "1" not empty.
>
> This is just neatnik-ism, since all the tests in the code are #ifdefs,
> but we shouldn't specify symbols as "Define to 1 ..." and then not
> actually define them that way.
>
> The usual policy here is not to fix problems with upstream directly,
> but to get them merged from upstream. Hence I don't think your patch
> should be merged, but we should re-sync with Postgres itself.
> --
> Michael

The issue is also existed on the origin/REL1_2_STABLE

2014-12-24 17:24 GMT+08:00 Jaimin Pan <jai...@gm...>:

> If configure on the other directory. pgxc_ctl can not be built correct.
> Here is the patch to fix the issue and add explicit dependency for make.
>

If configure on the other directory. pgxc_ctl can not be built correct.
Here is the patch to fix the issue and add explicit dependency for make.

============== setting connection information         ==============
CREATE NODE
CREATE NODE
CREATE NODE
CREATE NODE
CREATE NODE
CREATE NODE
 pgxc_pool_reload
------------------
 t
(1 row)

 pgxc_pool_reload
------------------
 t
(1 row)

============== creating database "regression"         ==============
CREATE DATABASE
ALTER DATABASE
============== running regression test queries        ==============
test tablespace               ... ok
parallel group (18 tests):  oid name varchar uuid int2 float4 char boolean
txid int4 text money int8 float8 bit enum numeric rangetypes
     boolean                  ... ok
     char                     ... ok
     name                     ... ok
     varchar                  ... ok
     text                     ... ok
     int2                     ... ok
     int4                     ... ok
     int8                     ... ok
     oid                      ... ok
     float4                   ... ok
     float8                   ... ok
     bit                      ... ok
     numeric                  ... ok
     txid                     ... ok
     uuid                     ... ok
     enum                     ... ok
     money                    ... ok
     rangetypes               ... ok
test strings                  ... ok
test numerology               ... ok
parallel group (19 tests):  lseg comments box circle polygon path time
timetz abstime reltime interval tinterval inet point macaddr timestamp
tstypes timestamptz date
     point                    ... ok
     lseg                     ... ok
     box                      ... ok
     path                     ... ok
     polygon                  ... ok
     circle                   ... ok
     date                     ... ok
     time                     ... ok
     timetz                   ... ok
     timestamp                ... ok
     timestamptz              ... ok
     interval                 ... ok
     abstime                  ... ok
     reltime                  ... ok
     tinterval                ... ok
     inet                     ... ok
     macaddr                  ... ok
     tstypes                  ... ok
     comments                 ... ok
parallel group (6 tests):  regex geometry type_sanity horology oidjoins
opr_sanity
     geometry                 ... ok
     horology                 ... ok
     regex                    ... ok
     oidjoins                 ... ok
     type_sanity              ... ok
     opr_sanity               ... ok
test insert                   ... ok
test create_function_1        ... ok
test create_type              ... ok
test create_table             ... ok
test create_function_2        ... ok
parallel group (2 tests):  copyselect copy
     copy                     ... ok
     copyselect               ... ok
parallel group (2 tests):  create_operator create_misc
     create_misc              ... ok
     create_operator          ... ok
parallel group (2 tests):  create_view create_index
     create_index             ... ok
     create_view              ... ok
test inherit                  ... ok
parallel group (10 tests):  create_cast create_aggregate typed_table
create_function_3 drop_if_exists create_table_like constraints
updatable_views vacuum triggers
     create_aggregate         ... ok
     create_function_3        ... ok
     create_cast              ... ok
     constraints              ... ok
     triggers                 ... ok
     create_table_like        ... ok
     typed_table              ... ok
     vacuum                   ... ok
     drop_if_exists           ... ok
     updatable_views          ... ok
test sanity_check             ... ok
test errors                   ... ok
test select                   ... ok
parallel group (19 tests):  select_distinct_on btree_index select_having
hash_index select_distinct case update delete namespace select_implicit
random transactions select_into union arrays subselect portals join
aggregates
     select_into              ... ok
     select_distinct          ... ok
     select_distinct_on       ... ok
     select_implicit          ... ok
     select_having            ... ok
     subselect                ... ok
     union                    ... ok
     case                     ... ok
     join                     ... FAILED
     aggregates               ... ok
     transactions             ... ok
     random                   ... ok
     portals                  ... ok
     arrays                   ... ok
     btree_index              ... ok
     hash_index               ... ok
     update                   ... ok
     namespace                ... ok
     delete                   ... ok
test prepared_xacts           ... ok
parallel group (4 tests):  security_label collate privileges matview
     privileges               ... ok
     security_label           ... ok
     collate                  ... ok
     matview                  ... ok
parallel group (3 tests):  psql misc alter_generic
     alter_generic            ... ok
     misc                     ... ok
     psql                     ... ok
test rules                    ... ok
test event_trigger            ... ok
parallel group (15 tests):  combocid xmlmap tsdicts portals_p2 guc
dependency functional_deps cluster json tsearch foreign_data select_views
window foreign_key bitmapops
     select_views             ... ok
     portals_p2               ... ok
     foreign_key              ... ok
     cluster                  ... ok
     dependency               ... ok
     guc                      ... ok
     bitmapops                ... ok
     combocid                 ... ok
     tsearch                  ... ok
     tsdicts                  ... ok
     foreign_data             ... ok
     window                   ... ok
     xmlmap                   ... ok
     functional_deps          ... ok
     json                     ... FAILED
test advisory_lock            ... ok
parallel group (19 tests):  largeobject polymorphism prepare limit
returning rowtypes temp plancache conversion copy2 sequence xml truncate
with rangefuncs domain plpgsql alter_table without_oid
     plancache                ... ok
     limit                    ... ok
     plpgsql                  ... FAILED
     copy2                    ... ok
     temp                     ... ok
     domain                   ... ok
     rangefuncs               ... ok
     prepare                  ... ok
     without_oid              ... ok
     conversion               ... ok
     truncate                 ... ok
     alter_table              ... ok
     sequence                 ... ok
     polymorphism             ... FAILED (test process exited with exit
code 2)
     rowtypes                 ... ok
     returning                ... ok
     largeobject              ... FAILED (test process exited with exit
code 2)
     with                     ... ok
     xml                      ... ok
test stats                    ... ok
test xc_create_function       ... ok
test xc_misc                  ... ok
parallel group (17 tests):  xc_params xc_sequence xc_limit xc_constraints
xc_sort xc_having xc_temp xc_copy xc_distkey xc_FQS_join xc_remote xc_FQS
xc_trigship xc_triggers xc_groupby xc_alter_table xc_returning
     xc_groupby               ... ok
     xc_distkey               ... ok
     xc_having                ... ok
     xc_temp                  ... ok
     xc_remote                ... ok
     xc_FQS                   ... ok
     xc_FQS_join              ... ok
     xc_copy                  ... ok
     xc_alter_table           ... ok
     xc_sequence              ... ok
     xc_triggers              ... ok
     xc_trigship              ... ok
     xc_constraints           ... ok
     xc_limit                 ... ok
     xc_sort                  ... ok
     xc_returning             ... ok
     xc_params                ... ok
test xc_node                  ... ok
test xc_prepared_xacts        ... ok
test xc_notrans_block         ... ok
============== shutting down postmaster               ==============
waiting for server to shut down... done
server stopped

========================
 5 of 158 tests failed.
========================

This is regression result on FreeBSD after this patch.
I also run the regression on CentOS6 x86_64，which get 3 of 158 tests failed.
I will check the failed tests later.

Jov
blog: http:amutu.com/blog <http://amutu.com/blog>

2014-12-24 10:39 GMT+08:00 Jov <am...@am...>:

> These changes already exist in PGXL,I port them to PGXC.
>
> the problem this patch solved(common in xl and xc):
> 1.make pgxc_ctl explicit depend bash（report error if there is no bash
> in PATH
> ）
> 2.change '#!/bin/bash' to '#/usr/bin/env bash' for all bash script
> 3.fix build error for missing .h for some type or maroc.
> 4.fix pool send and recv fds which transfer corrupt fds
>
> There also some changes only for PGXC:
> 1.build pgxc_ctl when cd contrib && make
> 2.fix build error for postgresMain which declare as return void but return
> a int.
> 3.fix warning : implicit declaration of function ‘heap_form_tuple’ is
> invalid in C99，which return int for a 64bit pointer，which cause runtime
> error.
>
> ref:
>
> http://sourceforge.net/p/postgres-xl/postgres-xl/ci/9f4da7c3527699ad66ed4af7088faa3ab8fad42c/
>
> http://sourceforge.net/p/postgres-xl/postgres-xl/ci/ccaa2d54927b73ace8efc686ea715daa99a72a76/
>
> http://sourceforge.net/p/postgres-xl/postgres-xl/ci/922f7aba30ee6a15a5cd4dabeeb254614d87d3b6/
>
>
> Jov
> blog: http:amutu.com/blog <http://amutu.com/blog>
>
>

On Tue, Dec 23, 2014 at 1:57 PM, Jaimin Pan <jai...@gm...> wrote:
> I check the PG repo master branch(latest commit in my view
> d69ffd6f035fe24483247bf9b2335d7474eaf31a).
> And there is no such error, seem no modified ever.
I disagree, per se this commit in Postgres:
commit: 5242fefb471d1fb2d0f35a33bde3570e19acd4b1
author: Tom Lane <tg...@ss...>
date: Sat, 15 Jun 2013 14:11:43 -0400
Be consistent about #define'ing configure symbols as "1" not empty.

This is just neatnik-ism, since all the tests in the code are #ifdefs,
but we shouldn't specify symbols as "Define to 1 ..." and then not
actually define them that way.

The usual policy here is not to fix problems with upstream directly,
but to get them merged from upstream. Hence I don't think your patch
should be merged, but we should re-sync with Postgres itself.
-- 
Michael

The patch also fix the problem that send multi command in one sql like "set
xxx to xxx; truncate  table xxx" which maybe cause "truncate table xxx" be
executed on datanode multi times.

2014-12-23 22:51 GMT+08:00 Jaimin Pan <jai...@gm...>:

> Hi all,
>
> I found that the set command handled by pool is not decent. Especially,
> the memory usage will grows up with the same set.
> Here is the patch to refectory and fix the potential problem.
>

Hi all,

I found that the set command handled by pool is not decent. Especially, the
memory usage will grows up with the same set.
Here is the patch to refectory and fix the potential problem.

I check the PG repo master branch(latest commit in my view
d69ffd6f035fe24483247bf9b2335d7474eaf31a).
And there is no such error, seem no modified ever.

2014-12-22 20:56 GMT+08:00 Koichi Suzuki <koi...@gm...>:

> This file was brought from PG repo.    Do you think it is specific to
> XC?   We may need to investigate how such difference came.
>
> Best;
> ---
> Koichi Suzuki
>
>
> 2014-12-22 18:06 GMT+09:00 Jaimin Pan <jai...@gm...>:
> > Sorry,Not just one.  Update the attachment.
> >
> > 2014-12-22 16:50 GMT+08:00 Jaimin Pan <jai...@gm...>:
> >>
> >> Hi all,
> >>
> >> I just found something maybe wrong on the branch origin/REL1_2_STABLE.
> >>
> >> Please have a check. Patch attached.
> >
> >
> >
> >
> ------------------------------------------------------------------------------
> > Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
> > from Actuate! Instantly Supercharge Your Business Reports and Dashboards
> > with Interactivity, Sharing, Native Excel Exports, App Integration & more
> > Get technology previously reserved for billion-dollar corporations, FREE
> >
> http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
> > _______________________________________________
> > Postgres-xc-developers mailing list
> > Pos...@li...
> > https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
> >
>

This file was brought from PG repo.    Do you think it is specific to
XC?   We may need to investigate how such difference came.

Best;
---
Koichi Suzuki


2014-12-22 18:06 GMT+09:00 Jaimin Pan <jai...@gm...>:
> Sorry,Not just one.  Update the attachment.
>
> 2014-12-22 16:50 GMT+08:00 Jaimin Pan <jai...@gm...>:
>>
>> Hi all,
>>
>> I just found something maybe wrong on the branch origin/REL1_2_STABLE.
>>
>> Please have a check. Patch attached.
>
>
>
> ------------------------------------------------------------------------------
> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
> from Actuate! Instantly Supercharge Your Business Reports and Dashboards
> with Interactivity, Sharing, Native Excel Exports, App Integration & more
> Get technology previously reserved for billion-dollar corporations, FREE
> http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
> _______________________________________________
> Postgres-xc-developers mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>

Sorry,Not just one.  Update the attachment.

2014-12-22 16:50 GMT+08:00 Jaimin Pan <jai...@gm...>:

> Hi all,
>
> I just found something maybe wrong on the branch origin/REL1_2_STABLE.
>
> Please have a check. Patch attached.
>

Hi all,

I just found something maybe wrong on the branch origin/REL1_2_STABLE.

Please have a check. Patch attached.

Yes, this may work because detained is almost postgres.    I’m afraid how you can make it useful, I mean, if you can create distributed/replicated tables via FDW in datanodes created manually.    Please let me know your idea.

Regards;
—
Koichi Suzuki

> 2014/12/21 22:46、Aris Setyawan <ari...@gm...> のメール：
> 
>> All the FDW statements are blocked
>> Anyway, please understand we need somebody to write a code to enable FDW at coordinator level and test it.
>> Do you have any other idea to do the same thing without FDW?
> 
> FDW statements only blocked in coordinator.
> So we can create fwd table manually in every data nodes (before join
> them in XC cluster), and then join them in XC cluster.
> 
> Please correct me if I'm wrong.
> 
> On 11/5/14, 鈴木 幸市 <ko...@in...> wrote:
>> Thank you Demai;
>> 
>> Unfortunately, XC does not support FDW at present.   All the FDW statements
>> are blocked.   It is not an architecture issue but an issue of development
>> and testing.   Now that XC support materialized view stored in datanodes, I
>> hope planner can handle FDW correctly.   Anyway, please understand we need
>> somebody to write a code to enable FDW at coordinator level and test it.
>> 
>> Do you have any other idea to do the same thing without FDW?
>> 
>> Regards;
>> ---
>> Koichi Suzuki
>> 
>> 2014/11/05 3:47、Demai Ni <ni...@gm...<mailto:ni...@gm...>> のメール：
>> 
>> hi, Koichi,
>> 
>> thanks for your response. I am trying to connect to a hdfs system, and
>> reading hdfs files through FDW. Assuming I have 10 files mapping to one
>> foreign table, and have 3 datanode on PG-XC, I'd like coordinator node to do
>> some simple scheduling so that each dataNode of PG-XC will read roughtly
>> same amount of data. That is why I'd like to hook a value(a String will be
>> fine) that generated by coordinator node, and visible to every data node.
>> 
>> Demai
>> 
>> Demai;
>> 
>> Anyway, could you describe your point more specifically?   What would
>> you do this in vanilla postgresql?  This will help to find how to do
>> it in XC.
>> 
>> Regards;
>> ---
>> Koichi Suzuki
>> 
>>>> hi, hackers,
>>>> 
>>>> I am looking for a simple way to pass a value(ideally a hashtable, and
>>>> use a
>>>> string for easy implementation for now), that is generated by
>>>> coordinator
>>>> node, and pass it to all data nodes. Plans may be one approach, I am
>>>> just
>>>> wondering whether there is a simpler hook?
>>>> 
>> 
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> Postgres-xc-developers mailing list
>> Pos...@li...<mailto:Pos...@li...>
>> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>> 
>> 
> 
> ------------------------------------------------------------------------------
> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
> from Actuate! Instantly Supercharge Your Business Reports and Dashboards
> with Interactivity, Sharing, Native Excel Exports, App Integration & more
> Get technology previously reserved for billion-dollar corporations, FREE
> http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
> _______________________________________________
> Postgres-xc-developers mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers

> All the FDW statements are blocked
> Anyway, please understand we need somebody to write a code to enable FDW at coordinator level and test it.
> Do you have any other idea to do the same thing without FDW?

FDW statements only blocked in coordinator.
So we can create fwd table manually in every data nodes (before join
them in XC cluster), and then join them in XC cluster.

Please correct me if I'm wrong.

On 11/5/14, 鈴木 幸市 <ko...@in...> wrote:
> Thank you Demai;
>
> Unfortunately, XC does not support FDW at present.   All the FDW statements
> are blocked.   It is not an architecture issue but an issue of development
> and testing.   Now that XC support materialized view stored in datanodes, I
> hope planner can handle FDW correctly.   Anyway, please understand we need
> somebody to write a code to enable FDW at coordinator level and test it.
>
> Do you have any other idea to do the same thing without FDW?
>
> Regards;
> ---
> Koichi Suzuki
>
> 2014/11/05 3:47、Demai Ni <ni...@gm...<mailto:ni...@gm...>> のメール：
>
> hi, Koichi,
>
> thanks for your response. I am trying to connect to a hdfs system, and
> reading hdfs files through FDW. Assuming I have 10 files mapping to one
> foreign table, and have 3 datanode on PG-XC, I'd like coordinator node to do
> some simple scheduling so that each dataNode of PG-XC will read roughtly
> same amount of data. That is why I'd like to hook a value(a String will be
> fine) that generated by coordinator node, and visible to every data node.
>
> Demai
>
> Demai;
>
> Anyway, could you describe your point more specifically?   What would
> you do this in vanilla postgresql?  This will help to find how to do
> it in XC.
>
> Regards;
> ---
> Koichi Suzuki
>
>>> hi, hackers,
>>>
>>> I am looking for a simple way to pass a value(ideally a hashtable, and
>>> use a
>>> string for easy implementation for now), that is generated by
>>> coordinator
>>> node, and pass it to all data nodes. Plans may be one approach, I am
>>> just
>>> wondering whether there is a simpler hook?
>>>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Postgres-xc-developers mailing list
> Pos...@li...<mailto:Pos...@li...>
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>
>

Thank you Demai;

Unfortunately, XC does not support FDW at present.   All the FDW statements are blocked.   It is not an architecture issue but an issue of development and testing.   Now that XC support materialized view stored in datanodes, I hope planner can handle FDW correctly.   Anyway, please understand we need somebody to write a code to enable FDW at coordinator level and test it.

Do you have any other idea to do the same thing without FDW?

Regards;
---
Koichi Suzuki

2014/11/05 3:47、Demai Ni <ni...@gm...<mailto:ni...@gm...>> のメール：

hi, Koichi,

thanks for your response. I am trying to connect to a hdfs system, and reading hdfs files through FDW. Assuming I have 10 files mapping to one foreign table, and have 3 datanode on PG-XC, I'd like coordinator node to do some simple scheduling so that each dataNode of PG-XC will read roughtly same amount of data. That is why I'd like to hook a value(a String will be fine) that generated by coordinator node, and visible to every data node.

Demai

Demai;

Anyway, could you describe your point more specifically?   What would
you do this in vanilla postgresql?  This will help to find how to do
it in XC.

Regards;
---
Koichi Suzuki

>> hi, hackers,
>>
>> I am looking for a simple way to pass a value(ideally a hashtable, and use a
>> string for easy implementation for now), that is generated by coordinator
>> node, and pass it to all data nodes. Plans may be one approach, I am just
>> wondering whether there is a simpler hook?
>>

------------------------------------------------------------------------------
_______________________________________________
Postgres-xc-developers mailing list
Pos...@li...<mailto:Pos...@li...>
https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers