Re: [Postgres-xc-general] Running PostGIS with Postgres-xc

[Kristian B. <kri...@gm...>]

I Just tested with pgxc 1.1 and as you said Koichi,  it works great. :-)

Thanks.
Kristian


2013/8/7 Kristian Bruun <kri...@gm...>

> I used pgxc 1.0.3, patched with
> https://www.stormdb.com/sites/default/files/downloads/postgis_xc.patchand with postgis intalled.
>
> Maybe I did something wrong in the configuration phase. I followed the
> guide from https://www.stormdb.com/content/enabling-postgis-postgres-xc
>
> So basically what i have done is (all running on the same node):
> *$ initgtm -D gtm -Z gtm
> $ initdb -D c1 --nodename=coord1
> $ initdb -D n1 --nodename=dnode1
> *
>
> *$ cat >> /home/postgresxc/pgxc/gtm/gtm.conf << EOF
> nodename = 'gtm'
> port = 20001
> EOF
> $
> $ cat >> /home/postgresxc/pgxc/c1/postgresql.conf << EOF
> gtm_port = 20001
> port = 20004
> pooler_port = 20008
> EOF
> $
> $ cat >> /home/postgresxc/pgxc/n1/postgresql.conf << EOF
> gtm_port = 20001
> port = 20006
> EOF
> $
> **$ gtm_ctl start -Z gtm -D data-gtm
> **$ pg_ctl start -D data-c1 -Z coordinator*
> $ psql -p 20001 -d postgres*
> *# create database myspatial;
> # \c myspstial
>
> Now if I run "create extension postgis;" or "create table spatial_ref_sys2 ...." i get the error.
>
> Am i missing something completely fundamental here?
>
> Anyway, i'll give it a try on pgxc 1.1 and let you know the result.
>
> Thanks.
>
> Kristian
>
> **
>
>
> 2013/8/7 Koichi Suzuki <koi...@gm...>
>
>> What version did you use?   I tested this statement with the latest 1.1
>> branch and found it runs successfully as follows:
>>
>> PGXC$ Psql
>> Selected coord3.
>> psql (PGXC 1.1beta, based on PG 9.2.4)
>> Type "help" for help.
>>
>> koichi=# CREATE TABLE spatial_ref_sys2 (
>> koichi(#           srid integer not null primary key
>> koichi(#         check (srid > 0 and srid <= 998999),
>> koichi(#           auth_name varchar(2048),
>> koichi(#           auth_srid integer,
>> koichi(#           srtext varchar(2048),
>> koichi(#           proj4text varchar(2048)
>> koichi(#  );
>> NOTICE:  CREATE TABLE / PRIMARY KEY will create implicit index
>> "spatial_ref_sys2_pkey" for table "spatial_ref_sys2"
>> CREATE TABLE
>> koichi=# select * from spatial_ref_sys2 ;
>>  srid | auth_name | auth_srid | srtext | proj4text
>> ------+-----------+-----------+--------+-----------
>> (0 rows)
>>
>> koichi=# \d spatial_ref_sys2
>>          Table "public.spatial_ref_sys2"
>>   Column   |          Type           | Modifiers
>> -----------+-------------------------+-----------
>>  srid      | integer                 | not null
>>  auth_name | character varying(2048) |
>>  auth_srid | integer                 |
>>  srtext    | character varying(2048) |
>>  proj4text | character varying(2048) |
>> Indexes:
>>     "spatial_ref_sys2_pkey" PRIMARY KEY, btree (srid)
>> Check constraints:
>>     "spatial_ref_sys2_srid_check" CHECK (srid > 0 AND srid <= 998999)
>>
>> koichi=#
>>
>> Regards;
>> ---
>> Koichi Suzuki
>>
>>
>> 2013/8/6 Kristian Bruun <kri...@gm...>
>>
>>> After digging more into to the problem, it seems like it's not postgis
>>> that's causing the problem, but something else.
>>>
>>> When I run the following command:
>>>
>>> CREATE TABLE spatial_ref_sys1 (
>>>           srid integer,
>>>           auth_name varchar(2048),
>>>           auth_srid integer,
>>>           srtext varchar(2048),
>>>           proj4text varchar(2048)
>>>  );
>>>
>>> It completes successfully, but running the same command where I specify
>>> the primary key
>>>
>>> CREATE TABLE spatial_ref_sys2 (
>>>           srid integer not null primary key
>>>         check (srid > 0 and srid <= 998999),
>>>           auth_name varchar(2048),
>>>           auth_srid integer,
>>>           srtext varchar(2048),
>>>           proj4text varchar(2048)
>>>  );
>>>
>>> it gives the *"server process (PID 9251) was terminated by signal 11:
>>> Segmentation fault" *error.
>>>
>>> Maybe this can help finding out what the problem might be.
>>>
>>> Regards,
>>> Kristian
>>>
>>>
>>>
>>> 2013/8/6 Andrei Martsinchyk <and...@gm...>
>>>
>>>> The tutorial was written some time back and may be out of date.
>>>> Hope we will find some time to look into and update the article.
>>>> The patch does have side effects, it is recommended to revert it after
>>>> installing.
>>>>
>>>>
>>>> 2013/8/6 鈴木 幸市 <ko...@in...>
>>>>
>>>>> I'm interested if the patch in the page does not have bad side
>>>>> effects.   It changes some of the error handling in XC core.
>>>>>
>>>>> Regards;
>>>>> ---
>>>>> Koichi Suzuki
>>>>>
>>>>> On 2013/08/06, at 10:21, Michael Paquier <mic...@gm...>
>>>>> wrote:
>>>>>
>>>>> > On Tue, Aug 6, 2013 at 9:56 AM, Koichi Suzuki <koi...@gm...>
>>>>> wrote:
>>>>> >> Hi,
>>>>> >>
>>>>> >> I think Mason Sharp has something on it.
>>>>> > And here you go...
>>>>> > https://www.stormdb.com/content/enabling-postgis-postgres-xc
>>>>> > --
>>>>> > Michael
>>>>> >
>>>>> >
>>>>> ------------------------------------------------------------------------------
>>>>> > Get your SQL database under version control now!
>>>>> > Version control is standard for application code, but databases
>>>>> havent
>>>>> > caught up. So what steps can you take to put your SQL databases under
>>>>> > version control? Why should you start doing it? Read more to find
>>>>> out.
>>>>> >
>>>>> http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
>>>>> > _______________________________________________
>>>>> > Postgres-xc-general mailing list
>>>>> > Pos...@li...
>>>>> > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general
>>>>> >
>>>>>
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> Get your SQL database under version control now!
>>>>> Version control is standard for application code, but databases havent
>>>>> caught up. So what steps can you take to put your SQL databases under
>>>>> version control? Why should you start doing it? Read more to find out.
>>>>>
>>>>> http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
>>>>> _______________________________________________
>>>>> Postgres-xc-general mailing list
>>>>> Pos...@li...
>>>>> https://lists.sourceforge.net/lists/listinfo/postgres-xc-general
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Andrei Martsinchyk
>>>>
>>>> StormDB - http://www.stormdb.com
>>>> The Database Cloud
>>>>
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Get your SQL database under version control now!
>>>> Version control is standard for application code, but databases havent
>>>> caught up. So what steps can you take to put your SQL databases under
>>>> version control? Why should you start doing it? Read more to find out.
>>>>
>>>> http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
>>>> _______________________________________________
>>>> Postgres-xc-general mailing list
>>>> Pos...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/postgres-xc-general
>>>>
>>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Get your SQL database under version control now!
>>> Version control is standard for application code, but databases havent
>>> caught up. So what steps can you take to put your SQL databases under
>>> version control? Why should you start doing it? Read more to find out.
>>>
>>> http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
>>> _______________________________________________
>>> Postgres-xc-general mailing list
>>> Pos...@li...
>>> https://lists.sourceforge.net/lists/listinfo/postgres-xc-general
>>>
>>>
>>
>