Menu
▾
▴
postgres-xc-developers — Postgres-XC hackers and developers
You can subscribe to this list here.
| 2010 |
Jan
|
Feb
|
Mar
|
Apr
(10) |
May
(17) |
Jun
(3) |
Jul
|
Aug
|
Sep
(8) |
Oct
(18) |
Nov
(51) |
Dec
(74) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2011 |
Jan
(47) |
Feb
(44) |
Mar
(44) |
Apr
(102) |
May
(35) |
Jun
(25) |
Jul
(56) |
Aug
(69) |
Sep
(32) |
Oct
(37) |
Nov
(31) |
Dec
(16) |
| 2012 |
Jan
(34) |
Feb
(127) |
Mar
(218) |
Apr
(252) |
May
(80) |
Jun
(137) |
Jul
(205) |
Aug
(159) |
Sep
(35) |
Oct
(50) |
Nov
(82) |
Dec
(52) |
| 2013 |
Jan
(107) |
Feb
(159) |
Mar
(118) |
Apr
(163) |
May
(151) |
Jun
(89) |
Jul
(106) |
Aug
(177) |
Sep
(49) |
Oct
(63) |
Nov
(46) |
Dec
(7) |
| 2014 |
Jan
(65) |
Feb
(128) |
Mar
(40) |
Apr
(11) |
May
(4) |
Jun
(8) |
Jul
(16) |
Aug
(11) |
Sep
(4) |
Oct
(1) |
Nov
(5) |
Dec
(16) |
| 2015 |
Jan
(5) |
Feb
|
Mar
(2) |
Apr
(5) |
May
(4) |
Jun
(12) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(4) |
| 2019 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
|
|
|
|
1
|
2
|
3
|
4
|
|
5
|
6
|
7
(13) |
8
(8) |
9
(12) |
10
(10) |
11
|
|
12
(1) |
13
(19) |
14
|
15
(22) |
16
(6) |
17
(20) |
18
|
|
19
|
20
(1) |
21
(1) |
22
(3) |
23
(4) |
24
(9) |
25
|
|
26
|
27
(4) |
28
(10) |
29
(3) |
30
(3) |
31
(2) |
|
|
From: Ashutosh B. <ash...@en...> - 2013-05-23 20:00:44
|
Hi All, While I hear Robert's presentation on query planning go wrong, I heard (first time) about MergeAppend plan. It looks like, we have something better to do with the way we are pushing the ORDER BY clauses and doing merge at the coordinator. Right now we are using Sort node and in ExecSort we start merging the rows. Instead, I think we should be using MergeAppend node. The only bad thing about this approach is MergeAppend node expects separate plans for each run of the sorted data. To do this, we need to replicate the RemoteQuery node as many times as there are nodes and put them in the list to the MergeAppend plan. I think that's going to solve the problem with materialisation (see mail thread "Using remote sorting for merge-join") and thus improve performance. It also takes away the need to have xc_node_id in the tupleslot of tuplestore. Obviously, simplifying the code. Any comments? Created 3613815 <https://sourceforge.net/tracker/?func=detail&aid=3613815&group_id=311227&atid=1310232>and assigned to me. <https://sourceforge.net/tracker/?func=detail&aid=3613815&group_id=311227&atid=1310232> On Mon, Dec 3, 2012 at 3:44 AM, Ashutosh Bapat < ash...@en...> wrote: > On Fri, Nov 30, 2012 at 9:37 AM, Michael Paquier > <mic...@gm...> wrote: > > Hi Ashutosh, > > > > Thanks for the patch. > > I found for the time being the following problems: > > 1) The patch has some whitespaces > > /home/michael/download/xc_sort.patch:16: trailing whitespace. > > > > /home/michael/download/xc_sort.patch:34: trailing whitespace. > > > > /home/michael/download/xc_sort.patch:307: trailing whitespace. > > return local_plan_left; > > /home/michael/download/xc_sort.patch:356: trailing whitespace. > > > > /home/michael/download/xc_sort.patch:360: trailing whitespace. > > > > Fixed. > > > error: patch failed: src/include/pgxc/execRemote.h:95 > > 2) the patch does not apply cleanly even by using "patch -p1"-like > commands > > When I sent the patch (more than a week before you replied) it was > based on the HEAD, but then there were some commits which created the > conflicts. The one attached should apply. > > > 3) No documentation about the new option enable_remotesort. > > 4) enable_remotesort is not listed in postgresql.conf. > > Please provide both documentation and reference in postgresql.conf.sample > > for transparency of the code. As an open source project it is important > to > > classify all the options available, for both the user and the developers. > > Added although, I still don't approve of it myself. > > > 5) What is cruelly missing with this patch are numbers. By how much this > > feature improves performance? > > Simple tests like a ORDER BY on a table with millions of rows would be > > enough, but as this is a performance feature, you should provide data > about > > how much those cases are improved. > > 6) A complain that I say for each planner-related patch in this > project.... > > This patch has a size of 200KB, 65% being updates on the EXPLAIN queries > of > > the XC query planning regression tests. This makes the commit tree > > unreadable and the evolution of the regression tests realy hard to follow > > because they need to be modified each time a planner optimization is > > introduced. We should move to a set of tests which is far more > > code-modification proof! > > This is planner code, so it's going to affect the plans that it > creates. In the test files we add EXPLAIN (with proper switches) to > check 1. whether the plans are coming as expected at that stage of > development, 2. Whether the clauses expected to be pushed down are > being indeed pushed down 3. the queries to be sent to the datanodes > are being crafted correctly. For every planner change, all the three > things above change, for the operation being planned and hence the > expected output changes are unavoidable. In fact, if you look at how > the expected output changing you get a idea of how correctly/wrong the > planner changes are made. Those diffs if go wrong, are great help to > me in finding problems earlier. During merge as well, if those tests > fail because of EXPLAIN outputs, that's a way to unwanted planner > changes early enough and correct them. Sorry, for the huge change, but > it's unavoidable. The testcases are intentionally prone to (planner) > code modification. > > > > > Regards, > > > > On Mon, Nov 26, 2012 at 8:42 PM, Ashutosh Bapat > > <ash...@en...> wrote: > >> > >> Hi All, > >> PFA patch which enables pushing down the ORDER BY clause or sorting to > the > >> Datanode/s through standard_planner(). > >> > >> This patch leverages the already existing merge sort mechanism for > >> RemoteQuery but now outside RemoteQuery using Sort plans. > >> > >> For a Sort plan it checks if all the expressions on which the result > needs > >> to be sorted are shippable and that the underlying tree allows to push > ORDER > >> BY to the Datanodes. If so, it includes the ORDER BY clause in the > query to > >> be sent to the Datanodes. If the number of Datanodes which participate > in > >> RemoteQuery is not 1, it adds a covering Sort node to merge the results > from > >> the Datanodes, otherwise, there is no covering Sort plan. > >> > >> The merge sort mechanism treats every Datanode as a tape and prefetches > >> the results from the Datanode corresponding to a dwindling tape. This is > >> enabled by setting the node from where to pull the next row before > calling > >> ExecProcNode on RemoteQueryState. > >> > >> The same mechanism is being used for Sort plan node under Group or Agg > >> nodes. > >> > >> The patch adds test xc_sort.sql for testing this functionality. It also > >> removes the now useless members sort and tuplesortstate from > RemoteQuery and > >> RemoteQueryState resp. > >> -- > >> Best Wishes, > >> Ashutosh Bapat > >> EntepriseDB Corporation > >> The Enterprise Postgres Company > >> > >> > >> > >> > ------------------------------------------------------------------------------ > >> Monitor your physical, virtual and cloud infrastructure from a single > >> web console. Get in-depth insight into apps, servers, databases, vmware, > >> SAP, cloud infrastructure, etc. Download 30-day Free Trial. > >> Pricing starts from $795 for 25 servers or applications! > >> http://p.sf.net/sfu/zoho_dev2dev_nov > >> _______________________________________________ > >> Postgres-xc-developers mailing list > >> Pos...@li... > >> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers > >> > > > > > > > > -- > > Michael Paquier > > http://michael.otacoo.com > > > > -- > Best Wishes, > Ashutosh Bapat > EntepriseDB Corporation > The Enterprise Postgres Company > -- Best Wishes, Ashutosh Bapat EntepriseDB Corporation The Postgres Database Company |
|
From: Abbas B. <abb...@en...> - 2013-05-23 04:56:56
|
On Thu, May 23, 2013 at 1:06 AM, Ahsan Hadi <ahs...@en...>wrote: > Abbas, > Are you planning to commit this soon? > No, This patch is dependent on the patch I sent in the email with subject "Patch to change name of a couple of variables to more general names" that is under review. Also in this email chain, Ashutosh has asked a few questions that I need to reply. > > > On Fri, May 17, 2013 at 5:26 AM, Ashutosh Bapat < > ash...@en...> wrote: > >> This looks good. Are there other ways where we can have UPDATE statement >> somewhere in the query tree list? Do we need to worry about such cases. >> >> >> On Fri, May 17, 2013 at 2:22 PM, Abbas Butt <abb...@en...>wrote: >> >>> >>> >>> On Thu, May 16, 2013 at 2:25 PM, Ashutosh Bapat < >>> ash...@en...> wrote: >>> >>>> Hi Abbas, >>>> Instead of fixing the first issue in pgxc_build_dml_statement(), is it >>>> possible to traverse the Query in validate_part_col_updatable() recursively >>>> to find UPDATE statements and apply partition column check? >>>> >>> >>> Yes. I have attached that patch for your feedback. If you think its ok I >>> can send the updated patch including the rest of the changes. >>> >>> >>>> That would cover all the possibilities, I guess. That also saves us >>>> much effort in case we come to support distribution column updation. >>>> >>>> I think, we need a generic solution to solve this command id issue, >>>> e.g. punching command id always and efficiently. But for now this suffices. >>>> Please log a bug/feature and put it in 1.2 bucket. >>>> >>> >>> Done. >>> (Artifact 3613498<https://sourceforge.net/tracker/?func=detail&aid=3613498&group_id=311227&atid=1310235> >>> ) >>> >>>> >>>> >>>> >>>> >>>> On Wed, May 15, 2013 at 5:31 AM, Abbas Butt < >>>> abb...@en...> wrote: >>>> >>>>> Adding developers mailing list. >>>>> >>>>> >>>>> On Wed, May 15, 2013 at 4:57 AM, Abbas Butt < >>>>> abb...@en...> wrote: >>>>> >>>>>> Hi, >>>>>> Attached please find a patch to fix test case with. >>>>>> There were two issues making the test to fail. >>>>>> 1. Updates to partition column were possible using syntax like >>>>>> WITH t AS (UPDATE y SET a=a+1 RETURNING *) SELECT * FROM t >>>>>> The patch blocks this syntax. >>>>>> >>>>>> 2. For a WITH query that updates a table in the main query and >>>>>> inserts a row in the same table in the WITH query we need to use >>>>>> command ID communication to remote nodes in order to >>>>>> maintain global data visibility. >>>>>> For example >>>>>> CREATE TEMP TABLE tab (id int,val text) DISTRIBUTE BY >>>>>> REPLICATION; >>>>>> INSERT INTO tab VALUES (1,'p1'); >>>>>> WITH wcte AS (INSERT INTO tab VALUES(42,'new') RETURNING id AS >>>>>> newid) >>>>>> UPDATE tab SET id = id + newid FROM wcte; >>>>>> The last query gets translated into the following multi-statement >>>>>> transaction on the primary datanode >>>>>> (a) START TRANSACTION ISOLATION LEVEL read committed READ WRITE >>>>>> (b) INSERT INTO tab (id, val) VALUES ($1, $2) RETURNING id -- >>>>>> (42,'new)' >>>>>> (c) SELECT id, val, ctid FROM ONLY tab WHERE true >>>>>> (d) UPDATE ONLY tab tab SET id = $1 WHERE (tab.ctid = $3) -- >>>>>> (43,(0,1)] >>>>>> (e) COMMIT TRANSACTION >>>>>> The command id of the select in step (c), should be such that >>>>>> it does not see the insert of step (b) >>>>>> >>>>>> Comments are welcome. >>>>>> >>>>>> Regards >>>>>> >>>>>> -- >>>>>> *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> >>>>> >>>>> >>>>> ------------------------------------------------------------------------------ >>>>> AlienVault Unified Security Management (USM) platform delivers complete >>>>> security visibility with the essential security capabilities. Easily >>>>> and >>>>> efficiently configure, manage, and operate all of your security >>>>> controls >>>>> from a single console and one unified framework. Download a free trial. >>>>> http://p.sf.net/sfu/alienvault_d2d >>>>> _______________________________________________ >>>>> Postgres-xc-core mailing list >>>>> Pos...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/postgres-xc-core >>>>> >>>>> >>>> >>>> >>>> -- >>>> 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 >> >> >> ------------------------------------------------------------------------------ >> AlienVault Unified Security Management (USM) platform delivers complete >> security visibility with the essential security capabilities. Easily and >> efficiently configure, manage, and operate all of your security controls >> from a single console and one unified framework. Download a free trial. >> http://p.sf.net/sfu/alienvault_d2d >> _______________________________________________ >> Postgres-xc-core mailing list >> Pos...@li... >> https://lists.sourceforge.net/lists/listinfo/postgres-xc-core >> >> > > > -- > 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. > -- -- *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> |
|
From: Abbas B. <abb...@en...> - 2013-05-23 04:41:50
|
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> |
|
From: Abbas B. <abb...@en...> - 2013-05-23 04:37:12
|
Its a random failure occurring due to ! ERROR: failed to send COMMIT command to node We can neglect it for now. On Thu, May 23, 2013 at 1:17 AM, Ahsan Hadi <ahs...@en...>wrote: > Abbas, > Can you take a look, the plpgsql test case is failing again in BF > regression from couple of days ago... > > > On Tue, May 7, 2013 at 6:43 AM, Ashutosh Bapat < > ash...@en...> wrote: > >> Ok, this is good to go then. >> >> >> On Tue, Apr 30, 2013 at 6:00 PM, Abbas Butt <abb...@en...>wrote: >> >>> >>> >>> On Tue, Apr 30, 2013 at 5:04 PM, Ashutosh Bapat < >>> ash...@en...> wrote: >>> >>>> Hi Abbas, >>>> This change looks confusing. The statements where you have added order >>>> by clause do not correspond to the statements where you have changed the >>>> output. Can you please explain this? >>>> >>> >>> The output of the test cases are changed because there was an error in >>> the expected output files of these test cases. These outputs have to be >>> modified (and the modified output is correct) because of your check in >>> 2608af3d5288607e8245fa10e74e7307bb1bb23d. >>> >>> The order by clause is added in test cases where the expected output was >>> already in order, but results were coming out to be in different order >>> depending on node configuration. >>> >>> >>>> >>>> Also, whenever you change .sql and need to change the .out for that, >>>> please change all the alt. expected output files. >>>> >>> >>> Sure >>> >>> >>>> >>>> >>>> On Thu, Apr 25, 2013 at 4:58 PM, Abbas Butt < >>>> abb...@en...> wrote: >>>> >>>>> Hi, >>>>> Attached please find patch to fix test case plpgsql. The test was >>>>> failing for some order by issues, Also there were some errors in expected >>>>> output. >>>>> >>>>> -- >>>>> *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_apr >>>>> _______________________________________________ >>>>> 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 >> >> >> ------------------------------------------------------------------------------ >> Learn Graph Databases - Download FREE O'Reilly Book >> "Graph Databases" is the definitive new guide to graph databases and >> their applications. This 200-page book is written by three acclaimed >> leaders in the field. The early access version is available now. >> Download your free book today! http://p.sf.net/sfu/neotech_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. > -- -- *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> |
