You can subscribe to this list here.
2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(2) |
Jun
|
Jul
|
Aug
(6) |
Sep
|
Oct
(19) |
Nov
(1) |
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2011 |
Jan
(12) |
Feb
(1) |
Mar
(4) |
Apr
(4) |
May
(32) |
Jun
(12) |
Jul
(11) |
Aug
(1) |
Sep
(6) |
Oct
(3) |
Nov
|
Dec
(10) |
2012 |
Jan
(11) |
Feb
(1) |
Mar
(3) |
Apr
(25) |
May
(53) |
Jun
(38) |
Jul
(103) |
Aug
(54) |
Sep
(31) |
Oct
(66) |
Nov
(77) |
Dec
(20) |
2013 |
Jan
(91) |
Feb
(86) |
Mar
(103) |
Apr
(107) |
May
(25) |
Jun
(37) |
Jul
(17) |
Aug
(59) |
Sep
(38) |
Oct
(78) |
Nov
(29) |
Dec
(15) |
2014 |
Jan
(23) |
Feb
(82) |
Mar
(118) |
Apr
(101) |
May
(103) |
Jun
(45) |
Jul
(6) |
Aug
(10) |
Sep
|
Oct
(32) |
Nov
|
Dec
(9) |
2015 |
Jan
(3) |
Feb
(5) |
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
(9) |
Aug
(4) |
Sep
(3) |
Oct
|
Nov
|
Dec
|
2016 |
Jan
(3) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2017 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2018 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(4) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
S | M | T | W | T | F | S |
---|---|---|---|---|---|---|
|
|
|
1
(2) |
2
(1) |
3
|
4
|
5
|
6
|
7
|
8
(1) |
9
(1) |
10
|
11
|
12
(1) |
13
(5) |
14
|
15
|
16
|
17
|
18
|
19
|
20
|
21
|
22
(4) |
23
(10) |
24
|
25
|
26
|
27
|
28
|
29
|
30
|
31
|
|
From: Nikhil S. <ni...@st...> - 2013-05-22 22:51:23
|
Hi Donald, This looks like a user permissions related internal bug in PGXC. Regards, Nikhils On Thu, May 23, 2013 at 3:13 AM, Donald Keyass <don...@gm...>wrote: > The testdb and user were the very last thing I created after I created the > node. > > > On Wed, May 22, 2013 at 4:54 PM, Koichi Suzuki <koi...@gm...>wrote: > >> Did you issue CREATE NODE before you create databases/roles? If you >> CREATE NODE after you create databases/users, they are not visible to other >> node and may fall into errors. When you create each node by initdb, you >> also create gtm's using initgtm, connect all the datanodes/coordinators to >> the gtm and then issue CREATE NODE before you create anothing else. >> >> >> You can visit >> https://github.com/koichi-szk/PGXC-Tools/blob/master/pgxc_ctl/pgxc_ctlto look into pgxc_ctl shell script, which takes care of configuration, >> failover, start and stop the cluster. init_all function will be helpful >> for you. This shows what you should do to initialize your cluster. The >> C-version of pgxc_ctl will be included in coming 1.1 release with new >> Postgres-XC feature. >> >> Regards; >> > > > > ------------------------------------------------------------------------------ > 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-general mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general > > -- StormDB - http://www.stormdb.com The Database Cloud |
From: Donald K. <don...@gm...> - 2013-05-22 21:43:20
|
The testdb and user were the very last thing I created after I created the node. On Wed, May 22, 2013 at 4:54 PM, Koichi Suzuki <koi...@gm...>wrote: > Did you issue CREATE NODE before you create databases/roles? If you > CREATE NODE after you create databases/users, they are not visible to other > node and may fall into errors. When you create each node by initdb, you > also create gtm's using initgtm, connect all the datanodes/coordinators to > the gtm and then issue CREATE NODE before you create anothing else. > > > You can visit > https://github.com/koichi-szk/PGXC-Tools/blob/master/pgxc_ctl/pgxc_ctl to > look into pgxc_ctl shell script, which takes care of configuration, > failover, start and stop the cluster. init_all function will be helpful > for you. This shows what you should do to initialize your cluster. The > C-version of pgxc_ctl will be included in coming 1.1 release with new > Postgres-XC feature. > > Regards; > |
From: Koichi S. <koi...@gm...> - 2013-05-22 20:54:51
|
Did you issue CREATE NODE before you create databases/roles? If you CREATE NODE after you create databases/users, they are not visible to other node and may fall into errors. When you create each node by initdb, you also create gtm's using initgtm, connect all the datanodes/coordinators to the gtm and then issue CREATE NODE before you create anothing else. You can visit https://github.com/koichi-szk/PGXC-Tools/blob/master/pgxc_ctl/pgxc_ctl to look into pgxc_ctl shell script, which takes care of configuration, failover, start and stop the cluster. init_all function will be helpful for you. This shows what you should do to initialize your cluster. The C-version of pgxc_ctl will be included in coming 1.1 release with new Postgres-XC feature. Regards; |
From: Donald K. <don...@gm...> - 2013-05-22 19:38:28
|
I'm running pg-xc 1.0.3 on debian linux (squeeze). I have 3 boxes. 1 for GTM and 2 for datanodes and coordinators. I have all three up and running. 1 GTM, 2 coordinators and 2 datanodes. I log in as system user postgres. I can create databases, create users, select, etc... So i created a database called testdb. In the testdb, I created a table called test_tab. I can query it as postgres user thru both coordinators. WHen I create a postgresql user: CREATE ROLE testuser WITH LOGIN PASSWORD 'testpass'; GRANT ALL PRIVILEGES ON DATABASE testdb to testuser; GRANT CONNECT ON DATABASE testdb TO testuser; GRANT ALL PRIVILEGES ON ALL TABLES IN SCHEMA public TO testuser; I can see the table, but when i select from it, i get: ERROR: Failed to get pooled connections I did this on each of the nodes: /usr/local/pgsql/bin/psql -c "CREATE NODE datanode0 WITH (TYPE = 'datanode', PORT = 5433, HOST = '100.100.10.170')" postgres /usr/local/pgsql/bin/psql -c "CREATE NODE datanode1 WITH (TYPE = 'datanode', PORT = 5433, HOST = '100.100.10.171')" postgres /usr/local/pgsql/bin/psql -c "CREATE NODE coord0 WITH (TYPE = 'coordinator', PORT = 5432, HOST = '100.100.10.170')" postgres /usr/local/pgsql/bin/psql -c "CREATE NODE coord1 WITH (TYPE = 'coordinator', PORT = 5432, HOST = '100.100.10.171')" postgres and /usr/local/pgsql/bin/psql -c "SELECT pgxc_pool_reload()" postgres where i got result of true. I even did: postgres=# select pgxc_pool_check(); pgxc_pool_check ----------------- t (1 row) and both are ok. when i do and lsof -i -n -P postgres 32131 postgres 3u IPv4 7245254 0t0 TCP *:5433 (LISTEN) postgres 32131 postgres 4u IPv6 7245255 0t0 TCP *:5433 (LISTEN) postgres 32141 postgres 3u IPv4 7245283 0t0 TCP *:5432 (LISTEN) postgres 32141 postgres 4u IPv6 7245284 0t0 TCP *:5432 (LISTEN) on both servers (data/coord) So I know they're listening. And two, i was able to create a database and table and insert and select from it as system user postgres. But when I create a postgresql user. It doesn't work. My Coord and DataNode pg_hba.conf is: # "local" is for Unix domain socket connections only local all postgres trust # IPv4 local connections: host all postgres 100.100.10.170/24 trust host all postgres 100.100.10.171/24 trust host all postgres 100.100.10.178/24 trust #GTM host all all 127.0.0.1/32 md5 host all all 100.100.10.0/24 md5 # IPv6 local connections: host all all ::1/128 md5 and in my pgxc_node: node_name | node_type | node_port | node_host | nodeis_primary | nodeis_preferred | node_id -----------+-----------+-----------+-------------+----------------+------------------+------------- datanode0 | D | 5433 | 100.100.10.170 | f | f | -96290283 datanode1 | D | 5433 | 100.100.10.171 | f | f | 888802358 coord1 | C | 5432 | 100.100.10.171 | f | f | 1885696643 coord0 | C | 5432 | 100.100.10.170 | f | f | -1944967855 for both servers. I have them on both coordinator and datanode databases. I'm @ a loss as to why a system user w/ admin privs can query but a postgres user w/ priviledges to query gets a : ERROR: Failed to get pooled connections I'm figuring it's a config issue somewhere, but i'm not sure as to where. Can some one point me in the right direction? Thank you in advance, Don. |