Re: [Postgres-xc-general] pg_statio_user_tables

[Tatsuo I. <is...@po...>]

Oh, I thought coordinator node knows everything about data node.

I did following:

execute direct on datanode1 'select * from pgxc_class as x join
pg_class as c on x.pcrelid = c.oid where c.relname =
''pgbench_accounts''';

on coordinator node and got 0 rows. Is that means pgbench_accounts
table is not distributed?

I did pgbench -k against coordinator node and I thought coordinator
automatically distributes data on each data node. Was this wrong
assumption?
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese: http://www.sraoss.co.jp

> Because pgxc_class and pg_class are both local to each node, oid is
> also local.   To query correctly, they should be issued using EXECUTE
> DIRECT statement.   Each EXECUTE DIRECT will return the result local
> to each node.
> 
> Regards;
> ----------
> Koichi Suzuki
> 
> 
> 2012/11/6 Tatsuo Ishii <is...@po...>:
>> I sent a query to coordinator node and got following result. Doesn't
>> this means table "pgbench_accounts" distributed?
>>
>> test=# select * from pgxc_class as x join pg_class as c on x.pcrelid = c.oid where c.relname = 'pgbench_accounts';
>> -[ RECORD 1 ]---+-----------------
>> pcrelid         | 16413
>> pclocatortype   | H
>> pcattnum        | 1
>> pchashalgorithm | 1
>> pchashbuckets   | 4096
>> nodeoids        | 16384 16385
>> relname         | pgbench_accounts
>> relnamespace    | 2200
>> reltype         | 16415
>> reloftype       | 0
>> relowner        | 10
>> relam           | 0
>> relfilenode     | 16419
>> reltablespace   | 0
>> relpages        | 0
>> reltuples       | 0
>> reltoastrelid   | 0
>> reltoastidxid   | 0
>> relhasindex     | t
>> relisshared     | f
>> relpersistence  | p
>> relkind         | r
>> relnatts        | 4
>> relchecks       | 0
>> relhasoids      | f
>> relhaspkey      | t
>> relhasrules     | f
>> relhastriggers  | f
>> relhassubclass  | f
>> relfrozenxid    | 78651
>> relacl          |
>> reloptions      | {fillfactor=100}
>>
>>> I tested with the current head (sorry) and found pg_statio_user_tables is available.
>>>
>>> Because this is not distributed tables (not distributed or replicated), query will return only local information of these tables.    Please use execute direct to query each node's statistics.
>>>
>>> Regards;
>>> ---
>>> Koichi Suzuki
>>>
>>> On Tue, 06 Nov 2012 15:02:37 +0900 (JST)
>>> Tatsuo Ishii <is...@po...> wrote:
>>>
>>>> Hi,
>>>>
>>>> It seems I cannot read pg_statio_user_tables from either coordinator or
>>>> data node. Is this a known limitation? I just would like to see how I
>>>> can confirm UPDATEs distributed among data nodes.
>>>> --
>>>> Tatsuo Ishii
>>>> SRA OSS, Inc. Japan
>>>> English: http://www.sraoss.co.jp/index_en.php
>>>> Japanese: http://www.sraoss.co.jp
>>>>
>>>> ------------------------------------------------------------------------------
>>>> LogMeIn Central: Instant, anywhere, Remote PC access and management.
>>>> Stay in control, update software, and manage PCs from one command center
>>>> Diagnose problems and improve visibility into emerging IT issues
>>>> Automate, monitor and manage. Do more in less time with Central
>>>> http://p.sf.net/sfu/logmein12331_d2d
>>>> _______________________________________________
>>>> Postgres-xc-general mailing list
>>>> Pos...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/postgres-xc-general
>>>>
>>
>> ------------------------------------------------------------------------------
>> LogMeIn Central: Instant, anywhere, Remote PC access and management.
>> Stay in control, update software, and manage PCs from one command center
>> Diagnose problems and improve visibility into emerging IT issues
>> Automate, monitor and manage. Do more in less time with Central
>> http://p.sf.net/sfu/logmein12331_d2d
>> _______________________________________________
>> Postgres-xc-general mailing list
>> Pos...@li...
>> https://lists.sourceforge.net/lists/listinfo/postgres-xc-general