Menu
▾
▴
postgres-xc-bugs — Bug report
You can subscribe to this list here.
| 2012 |
Jan
(2) |
Feb
|
Mar
|
Apr
(7) |
May
(27) |
Jun
(15) |
Jul
(11) |
Aug
(3) |
Sep
(1) |
Oct
|
Nov
(5) |
Dec
(1) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2013 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
|
Aug
|
Sep
(10) |
Oct
(19) |
Nov
(34) |
Dec
(6) |
| 2014 |
Jan
(31) |
Feb
(2) |
Mar
(4) |
Apr
|
May
(3) |
Jun
(6) |
Jul
(10) |
Aug
(2) |
Sep
|
Oct
|
Nov
(9) |
Dec
|
| 2015 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Koichi S. <koi...@gm...> - 2013-09-23 01:17:09
|
Sorry for the late response. Could you check pgxc_class catalog to see if the table is registered to this catalog as well? Usually, if you've created the table with conventional CREATE TABLE command from one of the coordinators, the definition should have propagated to all the coordinators. We're using COPY command in DBT-2 and does not have any significant problems. --- Koichi Suzuki 2013/9/19 West, William <ww...@uc...> > All, > > I am attempting to use the copy command (as I previously did > successfully in Postgres) to copy data from a file on the file system. When > I try to upload data to the XC instance I get a 'relation does not exist' > error. However if I check the metadata table, called tables, it is in there: > > postgres=# select * from information_schema.tables where table_type = > 'BASE TABLE'; > table_catalog | table_schema | table_name | table_type > | self_referencing_column_name | reference_generation | > user_defined_type_catalog | > user_defined_type_schema | user_defined_type_name | is_insertable_into | > is_typed | commit_action > > ---------------+--------------------+-------------------------+------------+------------------------------+----------------------+---------------------------+ > > --------------------------+------------------------+--------------------+----------+--------------- > postgres | staging | mutect | BASE > TABLE | | | > | > | | YES | > NO | > postgres | staging | vcf | BASE TABLE > | | | > | > | | YES | > NO | > postgres | information_schema | sql_features | BASE TABLE > | | | > | > | | YES | > NO | > postgres | gene | vcf | BASE TABLE > | | | > | > | | YES | > NO | > postgres | staging | source_downloads | BASE TABLE > | | | > | > | | YES | > NO | > postgres | pg_catalog | pg_cast | BASE TABLE > | | | > | > | | YES | > NO | > postgres | pg_catalog | pg_am | BASE TABLE > | | | > | > | | YES | > NO | > postgres | pg_catalog | pg_attrdef | BASE TABLE > | | | > | > | | YES | > NO | > postgres | public | products2 | BASE TABLE > | | | > | > | | YES | > NO | > postgres | information_schema | sql_sizing_profiles | BASE TABLE > | | | > | > | | YES | > NO | > postgres | information_schema | sql_sizing | BASE TABLE > | | | > | > | | YES | > NO | > postgres | information_schema | sql_parts | BASE TABLE > | | | > | > | | YES | > NO | > postgres | information_schema | sql_packages | BASE TABLE > | | | > | > | | YES | > NO | > postgres | information_schema | sql_languages | BASE TABLE > | | | > | > | | YES | > NO | > postgres | information_schema | sql_implementation_info | BASE TABLE > | | | > | > | | YES | > NO | > postgres | public | products | BASE TABLE > | | | > | > | | YES | > NO | > postgres | pg_catalog | pg_collation | BASE TABLE > | | | > | > | | YES | > NO | > postgres | pg_catalog | pg_seclabel | BASE TABLE > | | | > | > | | YES | > NO | > postgres | pg_catalog | pg_default_acl | BASE TABLE > | | | > | > | | YES | > NO | > postgres | pg_catalog | pg_foreign_table | BASE TABLE > | | | > | > | | YES | > NO | > postgres | pg_catalog | pgxc_group | BASE TABLE > | | | > | > | | YES | > NO | > postgres | pg_catalog | pgxc_node | BASE TABLE > | | | > | > | | YES | > NO | > postgres | pg_catalog | pgxc_class | BASE TABLE > | | | > | > | | YES | > NO | > postgres | pg_catalog | pg_foreign_server | BASE TABLE > | | | > | > | | YES | > NO | > postgres | pg_catalog | pg_foreign_data_wrapper | BASE TABLE > | | | > | > | | YES | > NO | > postgres | pg_catalog | pg_extension | BASE TABLE > | | | > | > | | YES | > NO | > postgres | pg_catalog | pg_ts_template | BASE TABLE > | | | > | > | | YES | > NO | > postgres=# \copy staging.mutect from '/tmp/20.mutect.call_stats.out'; > ERROR: relation "mutect" does not exist > > Is this a known bug (version 1.0.3) or is there a different command for > Copy in XC? If it is a bug is there any work around for bulk loading data? > > Thanks, > > Bill West > > > > ------------------------------------------------------------------------------ > LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99! > 1,500+ hours of tutorials including VisualStudio 2012, Windows 8, > SharePoint > 2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack > includes > Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13. > http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clktrk > _______________________________________________ > Postgres-xc-bugs mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-bugs > > |
|
From: Abbas B. <abb...@en...> - 2013-09-19 09:09:05
|
On Thu, Sep 19, 2013 at 3:17 AM, West, William <ww...@uc...> wrote: > All, > > I am attempting to use the copy command (as I previously did > successfully in Postgres) to copy data from a file on the file system. When > I try to upload data to the XC instance I get a 'relation does not exist' > error. However if I check the metadata table, called tables, it is in there: > > postgres=# select * from information_schema.tables where table_type = > 'BASE TABLE'; > table_catalog | table_schema | table_name | table_type > | self_referencing_column_name | reference_generation | > user_defined_type_catalog | > user_defined_type_schema | user_defined_type_name | is_insertable_into | > is_typed | commit_action > > ---------------+--------------------+-------------------------+------------+------------------------------+----------------------+---------------------------+ > > --------------------------+------------------------+--------------------+----------+--------------- > postgres | staging | mutect | BASE > TABLE | | | > | > | | YES | > NO | > postgres | staging | vcf | BASE TABLE > | | | > | > | | YES | > NO | > postgres | information_schema | sql_features | BASE TABLE > | | | > | > | | YES | > NO | > postgres | gene | vcf | BASE TABLE > | | | > | > | | YES | > NO | > postgres | staging | source_downloads | BASE TABLE > | | | > | > | | YES | > NO | > postgres | pg_catalog | pg_cast | BASE TABLE > | | | > | > | | YES | > NO | > postgres | pg_catalog | pg_am | BASE TABLE > | | | > | > | | YES | > NO | > postgres | pg_catalog | pg_attrdef | BASE TABLE > | | | > | > | | YES | > NO | > postgres | public | products2 | BASE TABLE > | | | > | > | | YES | > NO | > postgres | information_schema | sql_sizing_profiles | BASE TABLE > | | | > | > | | YES | > NO | > postgres | information_schema | sql_sizing | BASE TABLE > | | | > | > | | YES | > NO | > postgres | information_schema | sql_parts | BASE TABLE > | | | > | > | | YES | > NO | > postgres | information_schema | sql_packages | BASE TABLE > | | | > | > | | YES | > NO | > postgres | information_schema | sql_languages | BASE TABLE > | | | > | > | | YES | > NO | > postgres | information_schema | sql_implementation_info | BASE TABLE > | | | > | > | | YES | > NO | > postgres | public | products | BASE TABLE > | | | > | > | | YES | > NO | > postgres | pg_catalog | pg_collation | BASE TABLE > | | | > | > | | YES | > NO | > postgres | pg_catalog | pg_seclabel | BASE TABLE > | | | > | > | | YES | > NO | > postgres | pg_catalog | pg_default_acl | BASE TABLE > | | | > | > | | YES | > NO | > postgres | pg_catalog | pg_foreign_table | BASE TABLE > | | | > | > | | YES | > NO | > postgres | pg_catalog | pgxc_group | BASE TABLE > | | | > | > | | YES | > NO | > postgres | pg_catalog | pgxc_node | BASE TABLE > | | | > | > | | YES | > NO | > postgres | pg_catalog | pgxc_class | BASE TABLE > | | | > | > | | YES | > NO | > postgres | pg_catalog | pg_foreign_server | BASE TABLE > | | | > | > | | YES | > NO | > postgres | pg_catalog | pg_foreign_data_wrapper | BASE TABLE > | | | > | > | | YES | > NO | > postgres | pg_catalog | pg_extension | BASE TABLE > | | | > | > | | YES | > NO | > postgres | pg_catalog | pg_ts_template | BASE TABLE > | | | > | > | | YES | > NO | > postgres=# \copy staging.mutect from '/tmp/20.mutect.call_stats.out'; > ERROR: relation "mutect" does not exist > > Is this a known bug (version 1.0.3) or > I tried the use case on current master and could not reproduce the issue, Is it possible for you to upgrade to the latest release? > is there a different command for Copy in XC? > No, copy is supposed to work the same way it works on postgres. > > If it is a bug is there any work around for bulk loading data? > > > Thanks, > > Bill West > > > > ------------------------------------------------------------------------------ > LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99! > 1,500+ hours of tutorials including VisualStudio 2012, Windows 8, > SharePoint > 2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack > includes > Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13. > http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clktrk > _______________________________________________ > Postgres-xc-bugs mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-bugs > > -- -- *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> On Thu, Sep 19, 2013 at 3:17 AM, West, William <ww...@uc...> wrote: > All, > > I am attempting to use the copy command (as I previously did > successfully in Postgres) to copy data from a file on the file system. When > I try to upload data to the XC instance I get a 'relation does not exist' > error. However if I check the metadata table, called tables, it is in there: > > postgres=# select * from information_schema.tables where table_type = > 'BASE TABLE'; > table_catalog | table_schema | table_name | table_type > | self_referencing_column_name | reference_generation | > user_defined_type_catalog | > user_defined_type_schema | user_defined_type_name | is_insertable_into | > is_typed | commit_action > > ---------------+--------------------+-------------------------+------------+------------------------------+----------------------+---------------------------+ > > --------------------------+------------------------+--------------------+----------+--------------- > postgres | staging | mutect | BASE > TABLE | | | > | > | | YES | > NO | > postgres | staging | vcf | BASE TABLE > | | | > | > | | YES | > NO | > postgres | information_schema | sql_features | BASE TABLE > | | | > | > | | YES | > NO | > postgres | gene | vcf | BASE TABLE > | | | > | > | | YES | > NO | > postgres | staging | source_downloads | BASE TABLE > | | | > | > | | YES | > NO | > postgres | pg_catalog | pg_cast | BASE TABLE > | | | > | > | | YES | > NO | > postgres | pg_catalog | pg_am | BASE TABLE > | | | > | > | | YES | > NO | > postgres | pg_catalog | pg_attrdef | BASE TABLE > | | | > | > | | YES | > NO | > postgres | public | products2 | BASE TABLE > | | | > | > | | YES | > NO | > postgres | information_schema | sql_sizing_profiles | BASE TABLE > | | | > | > | | YES | > NO | > postgres | information_schema | sql_sizing | BASE TABLE > | | | > | > | | YES | > NO | > postgres | information_schema | sql_parts | BASE TABLE > | | | > | > | | YES | > NO | > postgres | information_schema | sql_packages | BASE TABLE > | | | > | > | | YES | > NO | > postgres | information_schema | sql_languages | BASE TABLE > | | | > | > | | YES | > NO | > postgres | information_schema | sql_implementation_info | BASE TABLE > | | | > | > | | YES | > NO | > postgres | public | products | BASE TABLE > | | | > | > | | YES | > NO | > postgres | pg_catalog | pg_collation | BASE TABLE > | | | > | > | | YES | > NO | > postgres | pg_catalog | pg_seclabel | BASE TABLE > | | | > | > | | YES | > NO | > postgres | pg_catalog | pg_default_acl | BASE TABLE > | | | > | > | | YES | > NO | > postgres | pg_catalog | pg_foreign_table | BASE TABLE > | | | > | > | | YES | > NO | > postgres | pg_catalog | pgxc_group | BASE TABLE > | | | > | > | | YES | > NO | > postgres | pg_catalog | pgxc_node | BASE TABLE > | | | > | > | | YES | > NO | > postgres | pg_catalog | pgxc_class | BASE TABLE > | | | > | > | | YES | > NO | > postgres | pg_catalog | pg_foreign_server | BASE TABLE > | | | > | > | | YES | > NO | > postgres | pg_catalog | pg_foreign_data_wrapper | BASE TABLE > | | | > | > | | YES | > NO | > postgres | pg_catalog | pg_extension | BASE TABLE > | | | > | > | | YES | > NO | > postgres | pg_catalog | pg_ts_template | BASE TABLE > | | | > | > | | YES | > NO | > postgres=# \copy staging.mutect from '/tmp/20.mutect.call_stats.out'; > ERROR: relation "mutect" does not exist > > Is this a known bug (version 1.0.3) or is there a different command for > Copy in XC? If it is a bug is there any work around for bulk loading data? > > Thanks, > > Bill West > > > > ------------------------------------------------------------------------------ > LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99! > 1,500+ hours of tutorials including VisualStudio 2012, Windows 8, > SharePoint > 2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack > includes > Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13. > http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clktrk > _______________________________________________ > Postgres-xc-bugs mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-bugs > > -- -- *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: West, W. <ww...@uc...> - 2013-09-18 22:18:06
|
All,
I am attempting to use the copy command (as I previously did successfully in Postgres) to copy data from a file on the file system. When I try to upload data to the XC instance I get a 'relation does not exist' error. However if I check the metadata table, called tables, it is in there:
postgres=# select * from information_schema.tables where table_type = 'BASE TABLE';
table_catalog | table_schema | table_name | table_type | self_referencing_column_name | reference_generation | user_defined_type_catalog |
user_defined_type_schema | user_defined_type_name | is_insertable_into | is_typed | commit_action
---------------+--------------------+-------------------------+------------+------------------------------+----------------------+---------------------------+
--------------------------+------------------------+--------------------+----------+---------------
postgres | staging | mutect | BASE TABLE | | | |
| | YES | NO |
postgres | staging | vcf | BASE TABLE | | | |
| | YES | NO |
postgres | information_schema | sql_features | BASE TABLE | | | |
| | YES | NO |
postgres | gene | vcf | BASE TABLE | | | |
| | YES | NO |
postgres | staging | source_downloads | BASE TABLE | | | |
| | YES | NO |
postgres | pg_catalog | pg_cast | BASE TABLE | | | |
| | YES | NO |
postgres | pg_catalog | pg_am | BASE TABLE | | | |
| | YES | NO |
postgres | pg_catalog | pg_attrdef | BASE TABLE | | | |
| | YES | NO |
postgres | public | products2 | BASE TABLE | | | |
| | YES | NO |
postgres | information_schema | sql_sizing_profiles | BASE TABLE | | | |
| | YES | NO |
postgres | information_schema | sql_sizing | BASE TABLE | | | |
| | YES | NO |
postgres | information_schema | sql_parts | BASE TABLE | | | |
| | YES | NO |
postgres | information_schema | sql_packages | BASE TABLE | | | |
| | YES | NO |
postgres | information_schema | sql_languages | BASE TABLE | | | |
| | YES | NO |
postgres | information_schema | sql_implementation_info | BASE TABLE | | | |
| | YES | NO |
postgres | public | products | BASE TABLE | | | |
| | YES | NO |
postgres | pg_catalog | pg_collation | BASE TABLE | | | |
| | YES | NO |
postgres | pg_catalog | pg_seclabel | BASE TABLE | | | |
| | YES | NO |
postgres | pg_catalog | pg_default_acl | BASE TABLE | | | |
| | YES | NO |
postgres | pg_catalog | pg_foreign_table | BASE TABLE | | | |
| | YES | NO |
postgres | pg_catalog | pgxc_group | BASE TABLE | | | |
| | YES | NO |
postgres | pg_catalog | pgxc_node | BASE TABLE | | | |
| | YES | NO |
postgres | pg_catalog | pgxc_class | BASE TABLE | | | |
| | YES | NO |
postgres | pg_catalog | pg_foreign_server | BASE TABLE | | | |
| | YES | NO |
postgres | pg_catalog | pg_foreign_data_wrapper | BASE TABLE | | | |
| | YES | NO |
postgres | pg_catalog | pg_extension | BASE TABLE | | | |
| | YES | NO |
postgres | pg_catalog | pg_ts_template | BASE TABLE | | | |
| | YES | NO |
postgres=# \copy staging.mutect from '/tmp/20.mutect.call_stats.out';
ERROR: relation "mutect" does not exist
Is this a known bug (version 1.0.3) or is there a different command for Copy in XC? If it is a bug is there any work around for bulk loading data?
Thanks,
Bill West
|
|
From: West, W. <ww...@uc...> - 2013-09-18 22:08:12
|
All,
I am attempting to use the copy command (as I previously did successfully in Postgres) to copy data from a file on the file system. When I try to upload data to the XC instance I get a 'relation does not exist' error. However if I check the metadata table, called tables, it is in there:
postgres=# select * from information_schema.tables where table_type = 'BASE TABLE';
table_catalog | table_schema | table_name | table_type | self_referencing_column_name | reference_generation | user_defined_type_catalog |
user_defined_type_schema | user_defined_type_name | is_insertable_into | is_typed | commit_action
---------------+--------------------+-------------------------+------------+------------------------------+----------------------+---------------------------+
--------------------------+------------------------+--------------------+----------+---------------
postgres | staging | mutect | BASE TABLE | | | |
| | YES | NO |
postgres | staging | vcf | BASE TABLE | | | |
| | YES | NO |
postgres | information_schema | sql_features | BASE TABLE | | | |
| | YES | NO |
postgres | gene | vcf | BASE TABLE | | | |
| | YES | NO |
postgres | staging | source_downloads | BASE TABLE | | | |
| | YES | NO |
postgres | pg_catalog | pg_cast | BASE TABLE | | | |
| | YES | NO |
postgres | pg_catalog | pg_am | BASE TABLE | | | |
| | YES | NO |
postgres | pg_catalog | pg_attrdef | BASE TABLE | | | |
| | YES | NO |
postgres | public | products2 | BASE TABLE | | | |
| | YES | NO |
postgres | information_schema | sql_sizing_profiles | BASE TABLE | | | |
| | YES | NO |
postgres | information_schema | sql_sizing | BASE TABLE | | | |
| | YES | NO |
postgres | information_schema | sql_parts | BASE TABLE | | | |
| | YES | NO |
postgres | information_schema | sql_packages | BASE TABLE | | | |
| | YES | NO |
postgres | information_schema | sql_languages | BASE TABLE | | | |
| | YES | NO |
postgres | information_schema | sql_implementation_info | BASE TABLE | | | |
| | YES | NO |
postgres | public | products | BASE TABLE | | | |
| | YES | NO |
postgres | pg_catalog | pg_collation | BASE TABLE | | | |
| | YES | NO |
postgres | pg_catalog | pg_seclabel | BASE TABLE | | | |
| | YES | NO |
postgres | pg_catalog | pg_default_acl | BASE TABLE | | | |
| | YES | NO |
postgres | pg_catalog | pg_foreign_table | BASE TABLE | | | |
| | YES | NO |
postgres | pg_catalog | pgxc_group | BASE TABLE | | | |
| | YES | NO |
postgres | pg_catalog | pgxc_node | BASE TABLE | | | |
| | YES | NO |
postgres | pg_catalog | pgxc_class | BASE TABLE | | | |
| | YES | NO |
postgres | pg_catalog | pg_foreign_server | BASE TABLE | | | |
| | YES | NO |
postgres | pg_catalog | pg_foreign_data_wrapper | BASE TABLE | | | |
| | YES | NO |
postgres | pg_catalog | pg_extension | BASE TABLE | | | |
| | YES | NO |
postgres | pg_catalog | pg_ts_template | BASE TABLE | | | |
| | YES | NO |
postgres=# \copy staging.mutect from '/tmp/20.mutect.call_stats.out';
ERROR: relation "mutect" does not exist
Is this a known bug or is there a different command for Copy in XC? If it is a bug is there any work around for bulk loading data?
Thanks,
Bill West
|
|
From: Javier H. <jhe...@ce...> - 2013-09-12 10:07:45
|
Hello,
============================================================================
POSTGRES-XC BUG REPORT TEMPLATE
============================================================================
Your name : Javier Hernandez
Your email address :jhe...@ce...
System Configuration:
---------------------
Architecture : Intel Xeon
Operating System : Debian 7.1
Postgres-XC version : Postgres-XC 1.1
Compiler used : gcc 4.7.2
Please enter a FULL description of your problem:
------------------------------------------------
I have a cluster with 2 datanodes and 1 coordinator, all of them have configured with 'md5' as the authentication method in pg_hba.conf.
I have a user with the same name and password in each of the nodes and I can access (psql) individually to each node
but I can't execute any SQL sentence in the coordinator*ERROR: Failed to get pooled connections*.
Changing to 'trust' authentication method in datanodes avoids the error but I need to secure the datanodes. Cretating a user with CREATE ROLE
in the coordinator and switch to 'md5' still fails, even using the new role.
According to the documentation it seems it should be supported.
If you know how this problem might be fixed, list the solution below:
---------------------------------------------------------------------*
Thank you,
--
Javier Hernández
Ingeniero de Bases de Datos
Centro de Estudios de Fisica del Cosmos de Aragon (ceFca)
http://www.cefca.es
Plza San Juan Nº 1, Planta 2ª
E-44001 Teruel (Spain)
Phone: +34 978 221266 Ext.1105
Fax: +34 978 611801
|
|
From: Koichi S. <koi...@gm...> - 2013-06-26 01:43:08
|
Hi, Javier;
Thank you very much for the report. I found the issue has been fixed in
the current head which will be available as 1.1 soon.
Please see the result.
----8<------------8<-----------
psql (PGXC 1.1devel, based on PG 9.2beta2)
Type "help" for help.
koichi=# CREATE TABLE test_count (val INTEGER, name VARCHAR(39));
CREATE TABLE
koichi=# INSERT INTO test_count VALUES (1, 'uno'), (2, 'dos');
INSERT 0 2
koichi=# begin;
BEGIN
koichi=# DECLARE cde CURSOR FOR SELECT count(*) FROM test_count;
DECLARE CURSOR
koichi=#
koichi=# fetch ALL from cde;
count
-------
2
(1 row)
koichi=# fetch ALL from cde;
count
-------
(0 rows)
koichi=# COMMIT;
COMMIT
koichi=#
---->8------------>8-----------
Regards;
----------
Koichi Suzuki
2013/6/26 Javier Hernandez <jhe...@ce...>
> Hello,
>
> ============================================================================
> POSTGRES-XC BUG REPORT TEMPLATE
> ============================================================================
>
> Your name : Javier Hernandez
> Your email address : jhe...@ce...
>
>
> System Configuration:
> ---------------------
> Architecture : Intel Xeon
>
> Operating System : Debian 6.0.7
>
> Postgres-XC version : Postgres-XC 1.0.3
>
> Compiler used : gcc 4.4.5
>
>
> Please enter a FULL description of your problem:
> ------------------------------------------------
>
> When I execute a SELECT count(*) aggregate function inside a query defined in a CURSOR returns incorrect values. It seems that returns the number of data nodes instead of computing the aggregate.
> (May is related with Bug *#3603394*, sorry for the guess)
>
>
> Please describe a way to repeat the problem. Please try to provide a
> concise reproducible example, if at all possible:
> ----------------------------------------------------------------------
>
> audit=# select * from pgxc_node;
> node_name | node_type | node_port | node_host | nodeis_primary | nodeis_preferred | node_id
> -----------+-----------+-----------+---------------+----------------+------------------+-------------
> coord1 | C | 5432 | localhost | f | f | 1885696643
> datanode1 | D | 54321 | localhost | f | f | 888802358
> datanode3 | D | 54322 | localhost | f | f | -1894792127
> datanode4 | D | 54322 | 192.168.56.61 | f | f | -1307323892
> datanode2 | D | 54321 | 192.168.56.61 | f | f | -905831925
> (5 rows)
>
> audit=# CREATE TABLE test_count (val INTEGER, name VARCHAR(39);
> audit=# INSERT INTO test_count VALUES (1, 'uno'), (2, 'dos');
> INSERT 0 2
> audit=# BEGIN;
> BEGIN
> audit=# DECLARE cde CURSOR FOR SELECT count(*) FROM test_count;
> DECLARE CURSOR
> audit=# fetch ALL from cde;
> count
> -------
> 4
> (1 row)
>
> audit=# fetch ALL from cde;
> count
> -------
> (0 rows)
>
> audit=# COMMIT;
> COMMIT
>
> Expected result is 2.
>
>
> If you know how this problem might be fixed, list the solution below:
> ---------------------------------------------------------------------*
> Sorry!
>
>
>
> Thanks,
>
> --
> Javier Hernández
> Ingeniero de Bases de Datos
> Centro de Estudios de Fisica del Cosmos de Aragon (ceFca)http://www.cefca.es
> Plza San Juan Nº 1, Planta 2ª
> E-44001 Teruel (Spain)
> Phone: +34 978 221266 Ext.1105
> Fax: +34 978 611801
>
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Postgres-xc-bugs mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-bugs
>
>
|
|
From: Javier H. <jhe...@ce...> - 2013-06-25 17:34:30
|
Hello,
============================================================================
POSTGRES-XC BUG REPORT TEMPLATE
============================================================================
Your name : Javier Hernandez
Your email address : jhe...@ce...
System Configuration:
---------------------
Architecture : Intel Xeon
Operating System : Debian 6.0.7
Postgres-XC version : Postgres-XC 1.0.3
Compiler used : gcc 4.4.5
Please enter a FULL description of your problem:
------------------------------------------------
When I execute a SELECT count(*) aggregate function inside a query defined in a CURSOR returns incorrect values. It seems that returns the number of data nodes instead of computing the aggregate.
(May is related with Bug*#3603394*, sorry for the guess)
Please describe a way to repeat the problem. Please try to provide a
concise reproducible example, if at all possible:
----------------------------------------------------------------------
audit=# select * from pgxc_node;
node_name | node_type | node_port | node_host | nodeis_primary | nodeis_preferred | node_id
-----------+-----------+-----------+---------------+----------------+------------------+-------------
coord1 | C | 5432 | localhost | f | f | 1885696643
datanode1 | D | 54321 | localhost | f | f | 888802358
datanode3 | D | 54322 | localhost | f | f | -1894792127
datanode4 | D | 54322 | 192.168.56.61 | f | f | -1307323892
datanode2 | D | 54321 | 192.168.56.61 | f | f | -905831925
(5 rows)
audit=# CREATE TABLE test_count (val INTEGER, name VARCHAR(39);
audit=# INSERT INTO test_count VALUES (1, 'uno'), (2, 'dos');
INSERT 0 2
audit=# BEGIN;
BEGIN
audit=# DECLARE cde CURSOR FOR SELECT count(*) FROM test_count;
DECLARE CURSOR
audit=# fetch ALL from cde;
count
-------
4
(1 row)
audit=# fetch ALL from cde;
count
-------
(0 rows)
audit=# COMMIT;
COMMIT
Expected result is 2.
If you know how this problem might be fixed, list the solution below:
---------------------------------------------------------------------*
Sorry!
Thanks,
--
Javier Hernández
Ingeniero de Bases de Datos
Centro de Estudios de Fisica del Cosmos de Aragon (ceFca)
http://www.cefca.es
Plza San Juan Nº 1, Planta 2ª
E-44001 Teruel (Spain)
Phone: +34 978 221266 Ext.1105
Fax: +34 978 611801
|
|
From: Hitoshi H. <hem...@la...> - 2013-01-18 07:38:10
|
Sorry for my late responce again. Thank you for your explanation. That resolved the problem. Howerver, it should be very hard for a normal user to get the point by himself, we guess. enforce_two_phase_commit is described in http://postgres-xc.sourceforge.net/docs/1_0/pg-xc-specifics.html There is no explicit pointer or suggestion to the above page in http://postgres-xc.sourceforge.net/docs/1_0/sql-createtable.html where CREATE TABLE syntax specified. Any planned improvements? -hemmi Michael Paquier さんは書きました: > This is not a bug. > The transaction that creates the temporary table is performed on > multiple nodes at the same time, so it needs to use 2PC. The table is > replicated, and PostgreSQL core cannot use 2PC on temporary objects. > So what you need to do is set enforce_two_phase_commit to off to > enforce the use of autocommit for such transactions involving > temporary objects. > > On Tue, Nov 13, 2012 at 5:06 PM, Hitoshi HEMMI > <hem...@la... <mailto:hem...@la...>> wrote: > > Hi, > > ============================================================================ > POSTGRES-XC BUG REPORT TEMPLATE > ============================================================================ > > Your name : Hitoshi Hemmi > Your email address : hem...@la... > <mailto:hem...@la...> > > System Configuration: > --------------------- > Architecture : x86_64 > > Operating Systems : CentOS release 6.2 x86_64 > > Postgres-XC version : Postgres-XC 1.0.1dev > > Description of problems: > ============================================== > > > a) ON COMMIT PRESERVE ROWS doesn't work > > ----------------------------------------------------------------------------------- > psql (PGXC 1.0.0, based on PG 9.1.4) > Type "help" for help. > > mydb=# DROP TABLE temp; > ERROR: table "temp" does not exist > mydb=# \d > List of relations > Schema | Name | Type | Owner > --------+--------------------+-------+---------- > public | area_digital | table | postgres > public | number | table | postgres > public | people | table | postgres > public | some_table | table | postgres > public | tenk1 | table | postgres > public | tenk1_with_oids | table | postgres > public | tenk1_without_oids | table | postgres > (7 rows) > > mydb=# BEGIN; > BEGIN > mydb=# CREATE GLOBAL TEMPORARY TABLE temp ( id SERIAL , text > VARCHAR(10) > ) ON COMMIT PRESERVE ROWS; > NOTICE: CREATE TABLE will create implicit sequence "temp_id_seq" for > serial column "temp.id <http://temp.id>" > INSERT INTO temp(text) VALUES('test'); > \d > CREATE TABLE > mydb=# INSERT INTO temp(text) VALUES('test'); > INSERT 0 1 > mydb=# INSERT INTO temp(text) VALUES('test'); > INSERT 0 1 > mydb=# INSERT INTO temp(text) VALUES('test'); > INSERT 0 1 > mydb=# \d > List of relations > Schema | Name | Type | Owner > -----------+--------------------+----------+---------- > pg_temp_2 | temp | table | postgres > pg_temp_2 | temp_id_seq | sequence | postgres > public | area_digital | table | postgres > public | number | table | postgres > public | people | table | postgres > public | some_table | table | postgres > public | tenk1 | table | postgres > public | tenk1_with_oids | table | postgres > public | tenk1_without_oids | table | postgres > (9 rows) > > mydb=# COMMIT; > ERROR: cannot PREPARE a transaction that has operated on temporary > tables > DETAIL: Disabling enforce_two_phase_commit is recommended to > enforce COMMIT > mydb=# \d > List of relations > Schema | Name | Type | Owner > --------+--------------------+-------+---------- > public | area_digital | table | postgres > public | number | table | postgres > public | people | table | postgres > public | some_table | table | postgres > public | tenk1 | table | postgres > public | tenk1_with_oids | table | postgres > public | tenk1_without_oids | table | postgres > (7 rows) > > mydb=# SELECT * FROM temp; > ERROR: relation "temp" does not exist > LINE 1: SELECT * FROM temp; > ^ > ----------------------------------------------------------------------------------- > > > > b) ON COMMIT DELETE ROWS doesn't work > > ----------------------------------------------------------------------------------- > psql (PGXC 1.0.0, based on PG 9.1.4) > Type "help" for help. > > mydb=# > mydb=# > mydb=# > mydb=# DROP TABLE temp; > ERROR: table "temp" does not exist > mydb=# \d > List of relations > Schema | Name | Type | Owner > --------+--------------------+-------+---------- > public | area_digital | table | postgres > public | number | table | postgres > public | people | table | postgres > public | some_table | table | postgres > public | tenk1 | table | postgres > public | tenk1_with_oids | table | postgres > public | tenk1_without_oids | table | postgres > (7 rows) > > mydb=# BEGIN; > BEGIN > mydb=# CREATE GLOBAL TEMPORARY TABLE temp ( id SERIAL , text > VARCHAR(10) > ) ON COMMIT DELETE ROWS; > NOTICE: CREATE TABLE will create implicit sequence "temp_id_seq" for > serial column "temp.id <http://temp.id>" > INSERT INTO temp(text) VALUES('test'); > INSERT INTO temp(text) VALUES('test'); > CREATE TABLE > mydb=# INSERT INTO temp(text) VALUES('test'); > INSERT 0 1 > mydb=# INSERT INTO temp(text) VALUES('test'); > INSERT 0 1 > mydb=# INSERT INTO temp(text) VALUES('test'); > INSERT 0 1 > mydb=# \d > List of relations > Schema | Name | Type | Owner > -----------+--------------------+----------+---------- > pg_temp_2 | temp | table | postgres > pg_temp_2 | temp_id_seq | sequence | postgres > public | area_digital | table | postgres > public | number | table | postgres > public | people | table | postgres > public | some_table | table | postgres > public | tenk1 | table | postgres > public | tenk1_with_oids | table | postgres > public | tenk1_without_oids | table | postgres > (9 rows) > > mydb=# COMMIT; > ERROR: cannot PREPARE a transaction that has operated on temporary > tables > DETAIL: Disabling enforce_two_phase_commit is recommended to > enforce COMMIT > mydb=# \d > List of relations > Schema | Name | Type | Owner > --------+--------------------+-------+---------- > public | area_digital | table | postgres > public | number | table | postgres > public | people | table | postgres > public | some_table | table | postgres > public | tenk1 | table | postgres > public | tenk1_with_oids | table | postgres > public | tenk1_without_oids | table | postgres > (7 rows) > > mydb=# SELECT * FROM temp; > ERROR: relation "temp" does not exist > LINE 1: SELECT * FROM temp; > ^ > ----------------------------------------------------------------------------------- > > -- > Hitoshi HEMMI > NTT Open Source Software Center > hem...@la... <mailto:hem...@la...> > (Please note that my address has changed.) > Tel:(03)5860-5115 > Fax:(03)5463-5490 > > > ------------------------------------------------------------------------------ > 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-bugs mailing list > Pos...@li... > <mailto:Pos...@li...> > https://lists.sourceforge.net/lists/listinfo/postgres-xc-bugs > > > > > -- > Michael Paquier > http://michael.otacoo.com -- Hitoshi HEMMI NTT Open Source Software Center hem...@la... (Please note that my address has changed.) Tel:(03)5860-5115 Fax:(03)5463-5490 |
|
From: Hitoshi H. <hem...@la...> - 2013-01-18 07:34:16
|
Sorry for my late responce. (Are you still there? ;-) We still have problem. Document you pointed says: "If DISTRIBUTE BY is not specified, columns with UNIQUE constraint will be chosen as the distribution key." What does it mean? We tried two possible scenarios, neither succeeded. 1) Specify unique constraint when CREATE TABLE -> syntax error test_db1=# CREATE TABLE uni_col2(no_uni1 integer, no_uni2 integer, uni1 integer unique) AS SELECT * FROM uni_col; ERROR: syntax error at or near "AS" LINE 1: ...i1 integer, no_uni2 integer, uni1 integer unique) AS SELECT ... 2) unique does not inherit by CREATE TABLE AS test_db1=# CREATE TABLE uni_col2(no_uni1, no_uni2, uni1) AS SELECT * FROM uni_col; INSERT 0 3 test_db1=# \d uni_col2 Table "public.uni_col2" Column | Type | Modifiers ---------+---------+----------- no_uni1 | integer | no_uni2 | integer | uni1 | integer | test_db1=# SELECT relid,relname FROM pg_stat_user_tables WHERE relname = 'uni_col2'; relid | relname -------+---------- 32848 | uni_col2 (1 row) test_db1=# SELECT * FROM pgxc_class WHERE pcrelid = 32848; pcrelid | pclocatortype | pcattnum | pchashalgorithm | pchashbuckets | nodeoids ---------+---------------+----------+-----------------+---------------+------------- 32848 | H | 1 | 1 | 4096 | 16385 16386 (1 row) By the way, we use v1.0.1. (Sorry) -hemmi Michael Paquier さんは書きました: > Even if you do not provide precise information, you need to know that > this is not a bug. > When using CREATE TABLE AS and select data from a table, you do not > copy the constraints of the table being scanned but only the data, > so it makes absolutely no sense to enforce the hash key on the column > uni1 for the table uni_col2. > Also, in the case of the 2nd table created, you do not specify any > distribution information with CREATE TABLE AS, so the distribution > chosen is hash with the first column whose type can be use to > calculate the hash keys, so in this case it is no_uni1, which is the > first column of table uni_col2. > > However, you can specify a distribute type for the newly-created table > as specified by the docs if you really want to enforce the hash to > uni1 for the 2nd table: > http://postgres-xc.sourceforge.net/docs/1_0/sql-createtableas.html > > On Tue, Nov 13, 2012 at 4:45 PM, Hitoshi HEMMI > <hem...@la... <mailto:hem...@la...>> wrote: > > Hi, list > > ============================================================================ > POSTGRES-XC BUG REPORT TEMPLATE > ============================================================================ > > Your name : Hitoshi Hemmi > Your email address : hem...@la... > <mailto:hem...@la...> > > > System Configuration: > --------------------- > Architecture : x86_64 > > Operating Systems : CentOS release 6.2 x86_64 > > Postgres-XC version : Postgres-XC 1.0.1dev > > Description of problems: > ============================================== > > 1) Create table "uni_col" with UNIQUE constraint on column unil > > mydb=# CREATE TABLE uni_col ( no_uni1 integer, no_uni2 integer, uni1 > integer unique); > NOTICE: CREATE TABLE / UNIQUE will create implicit index > "uni_col_uni1_key" for table "uni_col" > CREATE TABLE > > mydb=# \d uni_col > Table "public.uni_col" > Column | Type | Modifiers > ---------+---------+----------- > no_uni1 | integer | > no_uni2 | integer | > uni1 | integer | > Indexes: > "uni_col_uni1_key" UNIQUE CONSTRAINT, btree (uni1) > > > 2) Add some records to uni_col > > mydb=# INSERT INTO uni_col VALUES(1,1,1); > INSERT 0 1 > mydb=# INSERT INTO uni_col VALUES(2,2,2); > INSERT 0 1 > mydb=# INSERT INTO uni_col VALUES(3,3,3); > INSERT 0 1 > > mydb=# SELECT relid,relname FROM pg_stat_user_tables WHERE relname = > 'uni_col'; > relid | relname > --------+--------- > 114775 | uni_col > (1 row) > > > 3) See how uni_col is distributed and by what key > > mydb=# SELECT * FROM pgxc_class WHERE pcrelid = 114775; > pcrelid | pclocatortype | pcattnum | pchashalgorithm | pchashbuckets | > nodeoid > s > ---------+---------------+----------+-----------------+---------------+--------- > ---- > 114775 | H | 3 | 1 | 4096 | 16385 16 > 386 > (1 row) > > > 4) Create another table uni_col2 > > mydb=# CREATE TABLE uni_col2 AS SELECT * FROM uni_col; > INSERT 0 3 > > > 5) See how uni_col2 is distributed and by what key; > Expect uni1 is the key, but it isn't. > > mydb=# SELECT relid,relname FROM pg_stat_user_tables WHERE relname = > 'uni_col2'; > > relid | relname > --------+---------- > 114780 | uni_col2 > (1 row) > > mydb=# SELECT * FROM pgxc_class WHERE pcrelid = 114780; > pcrelid | pclocatortype | pcattnum | pchashalgorithm | pchashbuckets | > nodeoid > s > ---------+---------------+----------+-----------------+---------------+--------- > ---- > 114780 | H | 1 | 1 | 4096 | 16385 16 > 386 > (1 row) > > mydb=# \d uni_col2 > Table "public.uni_col2" > Column | Type | Modifiers > ---------+---------+----------- > no_uni1 | integer | > no_uni2 | integer | > uni1 | integer | > > -- > Hitoshi HEMMI > NTT Open Source Software Center > hem...@la... <mailto:hem...@la...> > (Please note that my address has changed.) > Tel:(03)5860-5115 > Fax:(03)5463-5490 > > > ------------------------------------------------------------------------------ > 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-bugs mailing list > Pos...@li... > <mailto:Pos...@li...> > https://lists.sourceforge.net/lists/listinfo/postgres-xc-bugs > > > > > -- > Michael Paquier > http://michael.otacoo.com -- Hitoshi HEMMI NTT Open Source Software Center hem...@la... (Please note that my address has changed.) Tel:(03)5860-5115 Fax:(03)5463-5490 |
|
From: yazuna <ya...@gm...> - 2012-12-12 14:25:32
|
Hello,
I'm testing postgres-xc to become eventually the main
storage/analytical solution for astronomical project dealing with
multiterabyte observational and processed astronomical data, so have
high hopes linked with it.
For the start I setup 3 datanodes, 1coordinator on the same box.
After minor tweaking I managed to port the schema to be compatible
(removed triggers, added distribution keys to unique indices) with XC
and managed to upload some data using copy interface.
I noticed however that sth like (extracted from the bash script):
psql -U $OUTHOST_DBUSER -d surveys -h $OUTHOST -p $OUTHOST_PORT -1 -c
"copy (select * from catalog where catalogid in (select * from
getAllSubCatalogs('$CATALOG_OUT'))) to stdin with null as '' csv" |
psql -U $INHOST_DBUSER -d $INHOST_DB -h $INHOST -p $INHOST_PORT -1 -e
-c "set constraints all deferred; copy catalog from stdout with csv;
update catalog set fowningcatalog=TRUE, fparentcatalog_catalogid =
null where catalogid = getcatalogid('$CATALOG_OUT');"
where the piped the Xc is the 2nd psql here we are pipe into
coordinator hangs and only sigkill is able to stop it. removing 'set
constraints all deferred;' (which works on PG9.1) seemed to heal the
problem and copy worked, it boils down to the pooler being in the
indefinite loop, consuming 100% of CPU.
(gdb)
262 while ((result = PQgetResult((PGconn *) conn)) != NULL)
(gdb)
265 PQclear(result);
(gdb)
262 while ((result = PQgetResult((PGconn *) conn)) != NULL)
(gdb)
265 PQclear(result);
(gdb)
262 while ((result = PQgetResult((PGconn *) conn)) != NULL)
(gdb) bt
#0 PGXCNodeSendSetQuery (conn=0x1082810, sql_command=<value optimized
out>) at pgxcnode.c:262
#1 0x00000000005c8fe7 in send_local_commands (agent=0x1071b10,
s=<value optimized out>) at poolmgr.c:1572
#2 agent_handle_input (agent=0x1071b10, s=<value optimized out>) at
poolmgr.c:1115
#3 0x00000000005c9d0f in PoolerLoop () at poolmgr.c:2402
#4 PoolManagerInit () at poolmgr.c:237
#5 0x00000000004c9d74 in AuxiliaryProcessMain (argc=2,
argv=0x7ffffa3e4a90) at bootstrap.c:421
#6 0x00000000006318d3 in StartChildProcess (type=PoolerProcess) at
postmaster.c:4713
#7 0x0000000000636204 in PostmasterMain (argc=<value optimized out>,
argv=<value optimized out>) at postmaster.c:1191
#8 0x00000000005cf3b0 in main (argc=5, argv=0x1050060) at main.c:199
Let me know if you need more data.
Cheers
Krzysztof
|
|
From: Michael P. <mic...@gm...> - 2012-11-13 12:55:30
|
This is not a bug.
The transaction that creates the temporary table is performed on multiple
nodes at the same time, so it needs to use 2PC. The table is replicated,
and PostgreSQL core cannot use 2PC on temporary objects. So what you need
to do is set enforce_two_phase_commit to off to enforce the use of
autocommit for such transactions involving temporary objects.
On Tue, Nov 13, 2012 at 5:06 PM, Hitoshi HEMMI
<hem...@la...>wrote:
> Hi,
>
>
> ============================================================================
> POSTGRES-XC BUG REPORT TEMPLATE
>
> ============================================================================
>
> Your name : Hitoshi Hemmi
> Your email address : hem...@la...
>
> System Configuration:
> ---------------------
> Architecture : x86_64
>
> Operating Systems : CentOS release 6.2 x86_64
>
> Postgres-XC version : Postgres-XC 1.0.1dev
>
> Description of problems:
> ==============================================
>
>
> a) ON COMMIT PRESERVE ROWS doesn't work
>
>
> -----------------------------------------------------------------------------------
> psql (PGXC 1.0.0, based on PG 9.1.4)
> Type "help" for help.
>
> mydb=# DROP TABLE temp;
> ERROR: table "temp" does not exist
> mydb=# \d
> List of relations
> Schema | Name | Type | Owner
> --------+--------------------+-------+----------
> public | area_digital | table | postgres
> public | number | table | postgres
> public | people | table | postgres
> public | some_table | table | postgres
> public | tenk1 | table | postgres
> public | tenk1_with_oids | table | postgres
> public | tenk1_without_oids | table | postgres
> (7 rows)
>
> mydb=# BEGIN;
> BEGIN
> mydb=# CREATE GLOBAL TEMPORARY TABLE temp ( id SERIAL , text VARCHAR(10)
> ) ON COMMIT PRESERVE ROWS;
> NOTICE: CREATE TABLE will create implicit sequence "temp_id_seq" for
> serial column "temp.id"
> INSERT INTO temp(text) VALUES('test');
> \d
> CREATE TABLE
> mydb=# INSERT INTO temp(text) VALUES('test');
> INSERT 0 1
> mydb=# INSERT INTO temp(text) VALUES('test');
> INSERT 0 1
> mydb=# INSERT INTO temp(text) VALUES('test');
> INSERT 0 1
> mydb=# \d
> List of relations
> Schema | Name | Type | Owner
> -----------+--------------------+----------+----------
> pg_temp_2 | temp | table | postgres
> pg_temp_2 | temp_id_seq | sequence | postgres
> public | area_digital | table | postgres
> public | number | table | postgres
> public | people | table | postgres
> public | some_table | table | postgres
> public | tenk1 | table | postgres
> public | tenk1_with_oids | table | postgres
> public | tenk1_without_oids | table | postgres
> (9 rows)
>
> mydb=# COMMIT;
> ERROR: cannot PREPARE a transaction that has operated on temporary tables
> DETAIL: Disabling enforce_two_phase_commit is recommended to enforce COMMIT
> mydb=# \d
> List of relations
> Schema | Name | Type | Owner
> --------+--------------------+-------+----------
> public | area_digital | table | postgres
> public | number | table | postgres
> public | people | table | postgres
> public | some_table | table | postgres
> public | tenk1 | table | postgres
> public | tenk1_with_oids | table | postgres
> public | tenk1_without_oids | table | postgres
> (7 rows)
>
> mydb=# SELECT * FROM temp;
> ERROR: relation "temp" does not exist
> LINE 1: SELECT * FROM temp;
> ^
>
> -----------------------------------------------------------------------------------
>
>
>
> b) ON COMMIT DELETE ROWS doesn't work
>
>
> -----------------------------------------------------------------------------------
> psql (PGXC 1.0.0, based on PG 9.1.4)
> Type "help" for help.
>
> mydb=#
> mydb=#
> mydb=#
> mydb=# DROP TABLE temp;
> ERROR: table "temp" does not exist
> mydb=# \d
> List of relations
> Schema | Name | Type | Owner
> --------+--------------------+-------+----------
> public | area_digital | table | postgres
> public | number | table | postgres
> public | people | table | postgres
> public | some_table | table | postgres
> public | tenk1 | table | postgres
> public | tenk1_with_oids | table | postgres
> public | tenk1_without_oids | table | postgres
> (7 rows)
>
> mydb=# BEGIN;
> BEGIN
> mydb=# CREATE GLOBAL TEMPORARY TABLE temp ( id SERIAL , text VARCHAR(10)
> ) ON COMMIT DELETE ROWS;
> NOTICE: CREATE TABLE will create implicit sequence "temp_id_seq" for
> serial column "temp.id"
> INSERT INTO temp(text) VALUES('test');
> INSERT INTO temp(text) VALUES('test');
> CREATE TABLE
> mydb=# INSERT INTO temp(text) VALUES('test');
> INSERT 0 1
> mydb=# INSERT INTO temp(text) VALUES('test');
> INSERT 0 1
> mydb=# INSERT INTO temp(text) VALUES('test');
> INSERT 0 1
> mydb=# \d
> List of relations
> Schema | Name | Type | Owner
> -----------+--------------------+----------+----------
> pg_temp_2 | temp | table | postgres
> pg_temp_2 | temp_id_seq | sequence | postgres
> public | area_digital | table | postgres
> public | number | table | postgres
> public | people | table | postgres
> public | some_table | table | postgres
> public | tenk1 | table | postgres
> public | tenk1_with_oids | table | postgres
> public | tenk1_without_oids | table | postgres
> (9 rows)
>
> mydb=# COMMIT;
> ERROR: cannot PREPARE a transaction that has operated on temporary tables
> DETAIL: Disabling enforce_two_phase_commit is recommended to enforce COMMIT
> mydb=# \d
> List of relations
> Schema | Name | Type | Owner
> --------+--------------------+-------+----------
> public | area_digital | table | postgres
> public | number | table | postgres
> public | people | table | postgres
> public | some_table | table | postgres
> public | tenk1 | table | postgres
> public | tenk1_with_oids | table | postgres
> public | tenk1_without_oids | table | postgres
> (7 rows)
>
> mydb=# SELECT * FROM temp;
> ERROR: relation "temp" does not exist
> LINE 1: SELECT * FROM temp;
> ^
>
> -----------------------------------------------------------------------------------
>
> --
> Hitoshi HEMMI
> NTT Open Source Software Center
> hem...@la...
> (Please note that my address has changed.)
> Tel:(03)5860-5115
> Fax:(03)5463-5490
>
>
>
> ------------------------------------------------------------------------------
> 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-bugs mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-bugs
>
--
Michael Paquier
http://michael.otacoo.com
|
|
From: Hitoshi H. <hem...@la...> - 2012-11-13 08:06:27
|
Hi,
============================================================================
POSTGRES-XC BUG REPORT TEMPLATE
============================================================================
Your name : Hitoshi Hemmi
Your email address : hem...@la...
System Configuration:
---------------------
Architecture : x86_64
Operating Systems : CentOS release 6.2 x86_64
Postgres-XC version : Postgres-XC 1.0.1dev
Description of problems:
==============================================
a) ON COMMIT PRESERVE ROWS doesn't work
-----------------------------------------------------------------------------------
psql (PGXC 1.0.0, based on PG 9.1.4)
Type "help" for help.
mydb=# DROP TABLE temp;
ERROR: table "temp" does not exist
mydb=# \d
List of relations
Schema | Name | Type | Owner
--------+--------------------+-------+----------
public | area_digital | table | postgres
public | number | table | postgres
public | people | table | postgres
public | some_table | table | postgres
public | tenk1 | table | postgres
public | tenk1_with_oids | table | postgres
public | tenk1_without_oids | table | postgres
(7 rows)
mydb=# BEGIN;
BEGIN
mydb=# CREATE GLOBAL TEMPORARY TABLE temp ( id SERIAL , text VARCHAR(10)
) ON COMMIT PRESERVE ROWS;
NOTICE: CREATE TABLE will create implicit sequence "temp_id_seq" for
serial column "temp.id"
INSERT INTO temp(text) VALUES('test');
\d
CREATE TABLE
mydb=# INSERT INTO temp(text) VALUES('test');
INSERT 0 1
mydb=# INSERT INTO temp(text) VALUES('test');
INSERT 0 1
mydb=# INSERT INTO temp(text) VALUES('test');
INSERT 0 1
mydb=# \d
List of relations
Schema | Name | Type | Owner
-----------+--------------------+----------+----------
pg_temp_2 | temp | table | postgres
pg_temp_2 | temp_id_seq | sequence | postgres
public | area_digital | table | postgres
public | number | table | postgres
public | people | table | postgres
public | some_table | table | postgres
public | tenk1 | table | postgres
public | tenk1_with_oids | table | postgres
public | tenk1_without_oids | table | postgres
(9 rows)
mydb=# COMMIT;
ERROR: cannot PREPARE a transaction that has operated on temporary tables
DETAIL: Disabling enforce_two_phase_commit is recommended to enforce COMMIT
mydb=# \d
List of relations
Schema | Name | Type | Owner
--------+--------------------+-------+----------
public | area_digital | table | postgres
public | number | table | postgres
public | people | table | postgres
public | some_table | table | postgres
public | tenk1 | table | postgres
public | tenk1_with_oids | table | postgres
public | tenk1_without_oids | table | postgres
(7 rows)
mydb=# SELECT * FROM temp;
ERROR: relation "temp" does not exist
LINE 1: SELECT * FROM temp;
^
-----------------------------------------------------------------------------------
b) ON COMMIT DELETE ROWS doesn't work
-----------------------------------------------------------------------------------
psql (PGXC 1.0.0, based on PG 9.1.4)
Type "help" for help.
mydb=#
mydb=#
mydb=#
mydb=# DROP TABLE temp;
ERROR: table "temp" does not exist
mydb=# \d
List of relations
Schema | Name | Type | Owner
--------+--------------------+-------+----------
public | area_digital | table | postgres
public | number | table | postgres
public | people | table | postgres
public | some_table | table | postgres
public | tenk1 | table | postgres
public | tenk1_with_oids | table | postgres
public | tenk1_without_oids | table | postgres
(7 rows)
mydb=# BEGIN;
BEGIN
mydb=# CREATE GLOBAL TEMPORARY TABLE temp ( id SERIAL , text VARCHAR(10)
) ON COMMIT DELETE ROWS;
NOTICE: CREATE TABLE will create implicit sequence "temp_id_seq" for
serial column "temp.id"
INSERT INTO temp(text) VALUES('test');
INSERT INTO temp(text) VALUES('test');
CREATE TABLE
mydb=# INSERT INTO temp(text) VALUES('test');
INSERT 0 1
mydb=# INSERT INTO temp(text) VALUES('test');
INSERT 0 1
mydb=# INSERT INTO temp(text) VALUES('test');
INSERT 0 1
mydb=# \d
List of relations
Schema | Name | Type | Owner
-----------+--------------------+----------+----------
pg_temp_2 | temp | table | postgres
pg_temp_2 | temp_id_seq | sequence | postgres
public | area_digital | table | postgres
public | number | table | postgres
public | people | table | postgres
public | some_table | table | postgres
public | tenk1 | table | postgres
public | tenk1_with_oids | table | postgres
public | tenk1_without_oids | table | postgres
(9 rows)
mydb=# COMMIT;
ERROR: cannot PREPARE a transaction that has operated on temporary tables
DETAIL: Disabling enforce_two_phase_commit is recommended to enforce COMMIT
mydb=# \d
List of relations
Schema | Name | Type | Owner
--------+--------------------+-------+----------
public | area_digital | table | postgres
public | number | table | postgres
public | people | table | postgres
public | some_table | table | postgres
public | tenk1 | table | postgres
public | tenk1_with_oids | table | postgres
public | tenk1_without_oids | table | postgres
(7 rows)
mydb=# SELECT * FROM temp;
ERROR: relation "temp" does not exist
LINE 1: SELECT * FROM temp;
^
-----------------------------------------------------------------------------------
--
Hitoshi HEMMI
NTT Open Source Software Center
hem...@la...
(Please note that my address has changed.)
Tel:(03)5860-5115
Fax:(03)5463-5490
|
|
From: Michael P. <mic...@gm...> - 2012-11-13 08:05:27
|
Even if you do not provide precise information, you need to know that this is not a bug. When using CREATE TABLE AS and select data from a table, you do not copy the constraints of the table being scanned but only the data, so it makes absolutely no sense to enforce the hash key on the column uni1 for the table uni_col2. Also, in the case of the 2nd table created, you do not specify any distribution information with CREATE TABLE AS, so the distribution chosen is hash with the first column whose type can be use to calculate the hash keys, so in this case it is no_uni1, which is the first column of table uni_col2. However, you can specify a distribute type for the newly-created table as specified by the docs if you really want to enforce the hash to uni1 for the 2nd table: http://postgres-xc.sourceforge.net/docs/1_0/sql-createtableas.html On Tue, Nov 13, 2012 at 4:45 PM, Hitoshi HEMMI <hem...@la...>wrote: > Hi, list > > > ============================================================================ > POSTGRES-XC BUG REPORT TEMPLATE > > ============================================================================ > > Your name : Hitoshi Hemmi > Your email address : hem...@la... > > > System Configuration: > --------------------- > Architecture : x86_64 > > Operating Systems : CentOS release 6.2 x86_64 > > Postgres-XC version : Postgres-XC 1.0.1dev > > Description of problems: > ============================================== > > 1) Create table "uni_col" with UNIQUE constraint on column unil > > mydb=# CREATE TABLE uni_col ( no_uni1 integer, no_uni2 integer, uni1 > integer unique); > NOTICE: CREATE TABLE / UNIQUE will create implicit index > "uni_col_uni1_key" for table "uni_col" > CREATE TABLE > > mydb=# \d uni_col > Table "public.uni_col" > Column | Type | Modifiers > ---------+---------+----------- > no_uni1 | integer | > no_uni2 | integer | > uni1 | integer | > Indexes: > "uni_col_uni1_key" UNIQUE CONSTRAINT, btree (uni1) > > > 2) Add some records to uni_col > > mydb=# INSERT INTO uni_col VALUES(1,1,1); > INSERT 0 1 > mydb=# INSERT INTO uni_col VALUES(2,2,2); > INSERT 0 1 > mydb=# INSERT INTO uni_col VALUES(3,3,3); > INSERT 0 1 > > mydb=# SELECT relid,relname FROM pg_stat_user_tables WHERE relname = > 'uni_col'; > relid | relname > --------+--------- > 114775 | uni_col > (1 row) > > > 3) See how uni_col is distributed and by what key > > mydb=# SELECT * FROM pgxc_class WHERE pcrelid = 114775; > pcrelid | pclocatortype | pcattnum | pchashalgorithm | pchashbuckets | > nodeoid > s > > ---------+---------------+----------+-----------------+---------------+--------- > ---- > 114775 | H | 3 | 1 | 4096 | 16385 16 > 386 > (1 row) > > > 4) Create another table uni_col2 > > mydb=# CREATE TABLE uni_col2 AS SELECT * FROM uni_col; > INSERT 0 3 > > > 5) See how uni_col2 is distributed and by what key; > Expect uni1 is the key, but it isn't. > > mydb=# SELECT relid,relname FROM pg_stat_user_tables WHERE relname = > 'uni_col2'; > > relid | relname > --------+---------- > 114780 | uni_col2 > (1 row) > > mydb=# SELECT * FROM pgxc_class WHERE pcrelid = 114780; > pcrelid | pclocatortype | pcattnum | pchashalgorithm | pchashbuckets | > nodeoid > s > > ---------+---------------+----------+-----------------+---------------+--------- > ---- > 114780 | H | 1 | 1 | 4096 | 16385 16 > 386 > (1 row) > > mydb=# \d uni_col2 > Table "public.uni_col2" > Column | Type | Modifiers > ---------+---------+----------- > no_uni1 | integer | > no_uni2 | integer | > uni1 | integer | > > -- > Hitoshi HEMMI > NTT Open Source Software Center > hem...@la... > (Please note that my address has changed.) > Tel:(03)5860-5115 > Fax:(03)5463-5490 > > > > ------------------------------------------------------------------------------ > 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-bugs mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-bugs > -- Michael Paquier http://michael.otacoo.com |
|
From: Michael P. <mic...@gm...> - 2012-11-13 07:49:06
|
I do not understand what means 1.0.1dev. Is it 1.0.1? Is it something else? Please provide at least a commit ID. On Tue, Nov 13, 2012 at 4:45 PM, Hitoshi HEMMI <hem...@la...>wrote: > Hi, list > > > ============================================================================ > POSTGRES-XC BUG REPORT TEMPLATE > > ============================================================================ > > Your name : Hitoshi Hemmi > Your email address : hem...@la... > > > System Configuration: > --------------------- > Architecture : x86_64 > > Operating Systems : CentOS release 6.2 x86_64 > > Postgres-XC version : Postgres-XC 1.0.1dev > > Description of problems: > ============================================== > > 1) Create table "uni_col" with UNIQUE constraint on column unil > > mydb=# CREATE TABLE uni_col ( no_uni1 integer, no_uni2 integer, uni1 > integer unique); > NOTICE: CREATE TABLE / UNIQUE will create implicit index > "uni_col_uni1_key" for table "uni_col" > CREATE TABLE > > mydb=# \d uni_col > Table "public.uni_col" > Column | Type | Modifiers > ---------+---------+----------- > no_uni1 | integer | > no_uni2 | integer | > uni1 | integer | > Indexes: > "uni_col_uni1_key" UNIQUE CONSTRAINT, btree (uni1) > > > 2) Add some records to uni_col > > mydb=# INSERT INTO uni_col VALUES(1,1,1); > INSERT 0 1 > mydb=# INSERT INTO uni_col VALUES(2,2,2); > INSERT 0 1 > mydb=# INSERT INTO uni_col VALUES(3,3,3); > INSERT 0 1 > > mydb=# SELECT relid,relname FROM pg_stat_user_tables WHERE relname = > 'uni_col'; > relid | relname > --------+--------- > 114775 | uni_col > (1 row) > > > 3) See how uni_col is distributed and by what key > > mydb=# SELECT * FROM pgxc_class WHERE pcrelid = 114775; > pcrelid | pclocatortype | pcattnum | pchashalgorithm | pchashbuckets | > nodeoid > s > > ---------+---------------+----------+-----------------+---------------+--------- > ---- > 114775 | H | 3 | 1 | 4096 | 16385 16 > 386 > (1 row) > > > 4) Create another table uni_col2 > > mydb=# CREATE TABLE uni_col2 AS SELECT * FROM uni_col; > INSERT 0 3 > > > 5) See how uni_col2 is distributed and by what key; > Expect uni1 is the key, but it isn't. > > mydb=# SELECT relid,relname FROM pg_stat_user_tables WHERE relname = > 'uni_col2'; > > relid | relname > --------+---------- > 114780 | uni_col2 > (1 row) > > mydb=# SELECT * FROM pgxc_class WHERE pcrelid = 114780; > pcrelid | pclocatortype | pcattnum | pchashalgorithm | pchashbuckets | > nodeoid > s > > ---------+---------------+----------+-----------------+---------------+--------- > ---- > 114780 | H | 1 | 1 | 4096 | 16385 16 > 386 > (1 row) > > mydb=# \d uni_col2 > Table "public.uni_col2" > Column | Type | Modifiers > ---------+---------+----------- > no_uni1 | integer | > no_uni2 | integer | > uni1 | integer | > > -- > Hitoshi HEMMI > NTT Open Source Software Center > hem...@la... > (Please note that my address has changed.) > Tel:(03)5860-5115 > Fax:(03)5463-5490 > > > > ------------------------------------------------------------------------------ > 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-bugs mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-bugs > -- Michael Paquier http://michael.otacoo.com |
|
From: Hitoshi H. <hem...@la...> - 2012-11-13 07:46:09
|
Hi, list ============================================================================ POSTGRES-XC BUG REPORT TEMPLATE ============================================================================ Your name : Hitoshi Hemmi Your email address : hem...@la... System Configuration: --------------------- Architecture : x86_64 Operating Systems : CentOS release 6.2 x86_64 Postgres-XC version : Postgres-XC 1.0.1dev Description of problems: ============================================== 1) Create table "uni_col" with UNIQUE constraint on column unil mydb=# CREATE TABLE uni_col ( no_uni1 integer, no_uni2 integer, uni1 integer unique); NOTICE: CREATE TABLE / UNIQUE will create implicit index "uni_col_uni1_key" for table "uni_col" CREATE TABLE mydb=# \d uni_col Table "public.uni_col" Column | Type | Modifiers ---------+---------+----------- no_uni1 | integer | no_uni2 | integer | uni1 | integer | Indexes: "uni_col_uni1_key" UNIQUE CONSTRAINT, btree (uni1) 2) Add some records to uni_col mydb=# INSERT INTO uni_col VALUES(1,1,1); INSERT 0 1 mydb=# INSERT INTO uni_col VALUES(2,2,2); INSERT 0 1 mydb=# INSERT INTO uni_col VALUES(3,3,3); INSERT 0 1 mydb=# SELECT relid,relname FROM pg_stat_user_tables WHERE relname = 'uni_col'; relid | relname --------+--------- 114775 | uni_col (1 row) 3) See how uni_col is distributed and by what key mydb=# SELECT * FROM pgxc_class WHERE pcrelid = 114775; pcrelid | pclocatortype | pcattnum | pchashalgorithm | pchashbuckets | nodeoid s ---------+---------------+----------+-----------------+---------------+--------- ---- 114775 | H | 3 | 1 | 4096 | 16385 16 386 (1 row) 4) Create another table uni_col2 mydb=# CREATE TABLE uni_col2 AS SELECT * FROM uni_col; INSERT 0 3 5) See how uni_col2 is distributed and by what key; Expect uni1 is the key, but it isn't. mydb=# SELECT relid,relname FROM pg_stat_user_tables WHERE relname = 'uni_col2'; relid | relname --------+---------- 114780 | uni_col2 (1 row) mydb=# SELECT * FROM pgxc_class WHERE pcrelid = 114780; pcrelid | pclocatortype | pcattnum | pchashalgorithm | pchashbuckets | nodeoid s ---------+---------------+----------+-----------------+---------------+--------- ---- 114780 | H | 1 | 1 | 4096 | 16385 16 386 (1 row) mydb=# \d uni_col2 Table "public.uni_col2" Column | Type | Modifiers ---------+---------+----------- no_uni1 | integer | no_uni2 | integer | uni1 | integer | -- Hitoshi HEMMI NTT Open Source Software Center hem...@la... (Please note that my address has changed.) Tel:(03)5860-5115 Fax:(03)5463-5490 |
|
From: Michael P. <mic...@gm...> - 2012-09-18 22:28:11
|
Hi, Just a notice for people sending emails to postgres-XC mailing lists... You need to register first to the mailing lists before sending a message to it. If you are not registered, ML administrators need to authorize manually the content of the message. This is particularly useful to prevent the pollution of spams here. It also takes time to approve the messages. You can register to the following mailing lists from the following links: - pos...@li..., https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers - pos...@li..., https://lists.sourceforge.net/lists/listinfo/postgres-xc-bugs - pos...@li..., https://lists.sourceforge.net/lists/listinfo/postgres-xc-general Thanks in advance, -- Michael Paquier http://michael.otacoo.com |
|
From: Michael P. <mic...@gm...> - 2012-08-21 22:50:42
|
Thanks for this report. It has already been fixed with this commit: https://github.com/postgres-xc/postgres-xc/commit/8a95ba5f4146dae958f4520869bad6593a3bf254 You can expect the tarball with the fix included when 1.0.1 is out some time next month. Thanks, On Wed, Aug 22, 2012 at 4:35 AM, Nick Maludy <nm...@gm...> wrote: > Your name : Nick Maludy > Your email address : nm...@gm... > > > System Configuration: > --------------------- > Architecture : Intel x86_64 > > Operating System : Scientific Linux 6 Kernel 2.6.32.59 > > Postgres-XC version : psql (PGXC 1.0.0, based on PG 9.1.4) > > Compiler used : gcc (GCC) 4.6.1 > > > Please enter a FULL description of your problem: > ------------------------------------------------ > I am receiving an error when trying to COPY from a table whose name is in CamelCase and is required to be quoted. > > I am able to successfully COPY this table if i use a COPY with SELECT. > > > > Please describe a way to repeat the problem. Please try to provide a > concise reproducible example, if at all possible: > ---------------------------------------------------------------------- > > $ psql test_db > > test_db=# CREATE TABLE "CamelCase" (i integer); > > CREATE TABLE > > test_db=# INSERT INTO "CamelCase" VALUES (3); > > INSERT 0 1 > > test_db=# COPY "CamelCase" TO STDOUT; > > ERROR: relation "camelcase" does not exist > > test_db=# COPY (SELECT * FROM "CamelCase") TO STDOUT; > > 3 > > > If you know how this problem might be fixed, list the solution below: > ---------------------------------------------------------------------* > > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Postgres-xc-bugs mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-bugs > > -- Michael Paquier http://michael.otacoo.com |
|
From: Nick M. <nm...@gm...> - 2012-08-21 19:36:21
|
Your name : Nick Maludy Your email address : nm...@gm... System Configuration: --------------------- Architecture : Intel x86_64 Operating System : Scientific Linux 6 Kernel 2.6.32.59 Postgres-XC version : psql (PGXC 1.0.0, based on PG 9.1.4) Compiler used : gcc (GCC) 4.6.1 Please enter a FULL description of your problem: ------------------------------------------------ I am receiving an error when trying to COPY from a table whose name is in CamelCase and is required to be quoted. I am able to successfully COPY this table if i use a COPY with SELECT. Please describe a way to repeat the problem. Please try to provide a concise reproducible example, if at all possible: ---------------------------------------------------------------------- $ psql test_db test_db=# CREATE TABLE "CamelCase" (i integer); CREATE TABLE test_db=# INSERT INTO "CamelCase" VALUES (3); INSERT 0 1 test_db=# COPY "CamelCase" TO STDOUT; ERROR: relation "camelcase" does not exist test_db=# COPY (SELECT * FROM "CamelCase") TO STDOUT; 3 If you know how this problem might be fixed, list the solution below: ---------------------------------------------------------------------* |
|
From: Michael P. <mic...@gm...> - 2012-08-10 09:27:12
|
Hi all, Sorry for sending this message to multiple mailing lists at the same time, but there were a couple of problems with the permissions of users inside 3 mailing lists we are using for Postgres-XC project. Those mailing lists are the general mailing list ( pos...@li...), the bug mailing list ( pos...@li...) and the hackers mailing list ( pos...@li...). For the sake of transparency to the community, let me explain what was happening... Our mailing lists are managed with mailman on SourceForge. For a reason I did not really understand, a portion of the users of those mailing lists had their messages moderated. This problem has been reported by Nikhil Sontakke but I found that a dozen of users on each mailing list was also impacted. Some users had their messages hidden, digested or moderated, and sometimes multiple filters were even set for the same user... The reason why I couldn't see that problem earlier? Well simply I couldn't receive the admin messages of the mailing lists as I was not registered there as an admin. So I went through all the users' permission and fixed it manually for everybody. This was not a huge work as XC community is not that huge compared to PostgreSQL ;) I am also registered there as an admin now, so there will *perhaps* not be that many problems in the future. Really sorry for the inconvenience. If you got any problems in the future or if you still have problems, you can contact me directly or send an email to the dedicated mailing list, I will take proper action. Best regards, -- Michael Paquier http://michael.otacoo.com |
|
From: Tomonari K. <kat...@po...> - 2012-07-12 11:36:46
|
thank you for response. I'll use "execute direct" when getting online backup. regards, (2012/07/12 16:11), Koichi Suzuki wrote: > Okay, so execute direct should be issued at any coordinator, not a datanode. > > Regards; > ---------- > Koichi Suzuki > > > 2012/7/12 Michael Paquier <mic...@gm...>: >> >> On Thu, Jul 12, 2012 at 3:31 PM, Tomonari Katsumata >> <kat...@po...> wrote: >>> Hi, All >>> >>> I'm testing online backup(PITR) on Postgres-XC 1.0.0. >>> And I have a problem. >>> >>> The manual says bellow. >>> http://postgres-xc.sourceforge.net/docs/1_0/continuous-archiving.html >>> This section describes PITR for PostgreSQL. >>> Because Coordinator and Datanode of Postgres-XC are >>> essentially PostgreSQLserver, you can do PITR for >>> each Coordinator and Datanode manually. >>> >>> >>> But, it is a difference between vanilla PostgreSQL and Postgres-XC. >>> When I do online backup against Datanode, I get some "WARNING" messages. >>> >>> [example]: Datanode is running with port 15432. >>> System Configuration: >>> --------------------- >>> Architecture : x86_64 >>> >>> Operating Systems : RHEL 5.7 x86_64 >>> >>> Postgres-XC version : Postgres-XC 1.0 >>> >>> Compilers used : gcc (GCC) 4.1.2 20080704 (Red Hat 4.1.2-51) >>> --------------------- >>> >>> Behabier: >>> --------------------- >>> $ psql postgres -p 15432 -c "SELECT pg_start_backup('test');" >>> WARNING: Do not have a GTM snapshot available >>> WARNING: Do not have a GTM snapshot available >>> pg_start_backup >>> ----------------- >>> 0/6000020 >>> (1 row) >>> >>> $ psql postgres -p 15432 -c "SELECT pg_stop_backup();" >>> WARNING: Do not have a GTM snapshot available >>> WARNING: Do not have a GTM snapshot available >>> NOTICE: pg_stop_backup complete, all required WAL segments have been >>> archived >>> pg_stop_backup >>> ---------------- >>> 0/60000A0 >>> (1 row) >>> --------------------- >>> >>> >>> Please tell me if it's ignorable WARNING or not. >>> And if I can not ignore the WARNING, do I have to >>> execute "pg_start/stop_backup"via "EXECUTE DIRECT" command ? >>> If so, the manual has to be revised soon. >> You cannot connect with an application directly to Datanodes as it won't >> guarantee global data consistency. >> So EXECUTE DIRECT is necessary here, I use it frequently with >> pg_start_backup and pg_stop_backup in HA configuration. >> I'll try to fix the documentation soon, thanks for pointing that. >> -- >> Michael Paquier >> http://michael.otacoo.com >> >> ------------------------------------------------------------------------------ >> Live Security Virtual Conference >> Exclusive live event will cover all the ways today's security and >> threat landscape has changed and how IT managers can respond. Discussions >> will include endpoint security, mobile security and the latest in malware >> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >> _______________________________________________ >> Postgres-xc-bugs mailing list >> Pos...@li... >> https://lists.sourceforge.net/lists/listinfo/postgres-xc-bugs >> -- -------------------------------------------- NTTソフトウェア株式会社 技術開発センター OSS基盤技術部門 TEL：045-212-7665 FAX：045-662-7856 E-Mail: kat...@po... -------------------------------------------- |
|
From: Koichi S. <koi...@gm...> - 2012-07-12 07:11:17
|
Okay, so execute direct should be issued at any coordinator, not a datanode. Regards; ---------- Koichi Suzuki 2012/7/12 Michael Paquier <mic...@gm...>: > > > On Thu, Jul 12, 2012 at 3:31 PM, Tomonari Katsumata > <kat...@po...> wrote: >> >> Hi, All >> >> I'm testing online backup(PITR) on Postgres-XC 1.0.0. >> And I have a problem. >> >> The manual says bellow. >> http://postgres-xc.sourceforge.net/docs/1_0/continuous-archiving.html >> This section describes PITR for PostgreSQL. >> Because Coordinator and Datanode of Postgres-XC are >> essentially PostgreSQLserver, you can do PITR for >> each Coordinator and Datanode manually. >> >> >> But, it is a difference between vanilla PostgreSQL and Postgres-XC. >> When I do online backup against Datanode, I get some "WARNING" messages. >> >> [example]: Datanode is running with port 15432. >> System Configuration: >> --------------------- >> Architecture : x86_64 >> >> Operating Systems : RHEL 5.7 x86_64 >> >> Postgres-XC version : Postgres-XC 1.0 >> >> Compilers used : gcc (GCC) 4.1.2 20080704 (Red Hat 4.1.2-51) >> --------------------- >> >> Behabier: >> --------------------- >> $ psql postgres -p 15432 -c "SELECT pg_start_backup('test');" >> WARNING: Do not have a GTM snapshot available >> WARNING: Do not have a GTM snapshot available >> pg_start_backup >> ----------------- >> 0/6000020 >> (1 row) >> >> $ psql postgres -p 15432 -c "SELECT pg_stop_backup();" >> WARNING: Do not have a GTM snapshot available >> WARNING: Do not have a GTM snapshot available >> NOTICE: pg_stop_backup complete, all required WAL segments have been >> archived >> pg_stop_backup >> ---------------- >> 0/60000A0 >> (1 row) >> --------------------- >> >> >> Please tell me if it's ignorable WARNING or not. >> And if I can not ignore the WARNING, do I have to >> execute "pg_start/stop_backup"via "EXECUTE DIRECT" command ? >> If so, the manual has to be revised soon. > > You cannot connect with an application directly to Datanodes as it won't > guarantee global data consistency. > So EXECUTE DIRECT is necessary here, I use it frequently with > pg_start_backup and pg_stop_backup in HA configuration. > I'll try to fix the documentation soon, thanks for pointing that. > -- > Michael Paquier > http://michael.otacoo.com > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Postgres-xc-bugs mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-bugs > |
|
From: Michael P. <mic...@gm...> - 2012-07-12 07:02:52
|
On Thu, Jul 12, 2012 at 3:31 PM, Tomonari Katsumata < kat...@po...> wrote: > Hi, All > > I'm testing online backup(PITR) on Postgres-XC 1.0.0. > And I have a problem. > > The manual says bellow. > http://postgres-xc.sourceforge.net/docs/1_0/continuous-archiving.html > This section describes PITR for PostgreSQL. > Because Coordinator and Datanode of Postgres-XC are > essentially PostgreSQLserver, you can do PITR for > each Coordinator and Datanode manually. > > > But, it is a difference between vanilla PostgreSQL and Postgres-XC. > When I do online backup against Datanode, I get some "WARNING" messages. > > [example]: Datanode is running with port 15432. > System Configuration: > --------------------- > Architecture : x86_64 > > Operating Systems : RHEL 5.7 x86_64 > > Postgres-XC version : Postgres-XC 1.0 > > Compilers used : gcc (GCC) 4.1.2 20080704 (Red Hat 4.1.2-51) > --------------------- > > Behabier: > --------------------- > $ psql postgres -p 15432 -c "SELECT pg_start_backup('test');" > WARNING: Do not have a GTM snapshot available > WARNING: Do not have a GTM snapshot available > pg_start_backup > ----------------- > 0/6000020 > (1 row) > > $ psql postgres -p 15432 -c "SELECT pg_stop_backup();" > WARNING: Do not have a GTM snapshot available > WARNING: Do not have a GTM snapshot available > NOTICE: pg_stop_backup complete, all required WAL segments have been > archived > pg_stop_backup > ---------------- > 0/60000A0 > (1 row) > --------------------- > > > Please tell me if it's ignorable WARNING or not. > And if I can not ignore the WARNING, do I have to > execute "pg_start/stop_backup"via "EXECUTE DIRECT" command ? > If so, the manual has to be revised soon. > You cannot connect with an application directly to Datanodes as it won't guarantee global data consistency. So EXECUTE DIRECT is necessary here, I use it frequently with pg_start_backup and pg_stop_backup in HA configuration. I'll try to fix the documentation soon, thanks for pointing that. -- Michael Paquier http://michael.otacoo.com |
|
From: Tomonari K. <kat...@po...> - 2012-07-12 06:55:58
|
Hi, All I'm testing online backup(PITR) on Postgres-XC 1.0.0. And I have a problem. The manual says bellow. http://postgres-xc.sourceforge.net/docs/1_0/continuous-archiving.html This section describes PITR for PostgreSQL. Because Coordinator and Datanode of Postgres-XC are essentially PostgreSQLserver, you can do PITR for each Coordinator and Datanode manually. But, it is a difference between vanilla PostgreSQL and Postgres-XC. When I do online backup against Datanode, I get some "WARNING" messages. [example]: Datanode is running with port 15432. System Configuration: --------------------- Architecture : x86_64 Operating Systems : RHEL 5.7 x86_64 Postgres-XC version : Postgres-XC 1.0 Compilers used : gcc (GCC) 4.1.2 20080704 (Red Hat 4.1.2-51) --------------------- Behabier: --------------------- $ psql postgres -p 15432 -c "SELECT pg_start_backup('test');" WARNING: Do not have a GTM snapshot available WARNING: Do not have a GTM snapshot available pg_start_backup ----------------- 0/6000020 (1 row) $ psql postgres -p 15432 -c "SELECT pg_stop_backup();" WARNING: Do not have a GTM snapshot available WARNING: Do not have a GTM snapshot available NOTICE: pg_stop_backup complete, all required WAL segments have been archived pg_stop_backup ---------------- 0/60000A0 (1 row) --------------------- Please tell me if it's ignorable WARNING or not. And if I can not ignore the WARNING, do I have to execute "pg_start/stop_backup"via "EXECUTE DIRECT" command ? If so, the manual has to be revised soon. regards, ---- Tomonari Katsumata |
|
From: Hitoshi H. <hem...@la...> - 2012-07-11 07:01:26
|
Hi list, We have been testing GTM HA feature, and found a problem: once gtm got failed, if someone or some AP accessed to coordinator before gtm failover complete, gtm_standby can never be reconnect to the cluster. ============================================================================ POSTGRES-XC BUG REPORT TEMPLATE ============================================================================ Your name : Hitoshi Hemmi Your email address : hem...@la... System Configuration: --------------------- Architecture : x86_64 Operating Systems : CentOS release 6.2 x86_64 Postgres-XC version : Postgres-XC 1.0 Compilers used : gcc (GCC) 4.4.6 20110731 (Red Hat 4.4.6-3) Description of problems: ============================================== 1. Simmulated failure of gtm gtm_ctl stop -Z gtm -m immediate -D /home/postgres/data/gtm 2. Unluckily someone access to a coordinator psql -p 5432 -c "SELECT * FROM pgxc_node;" 3. Promotion of gtm_standby gtm_ctl promote -Z gtm -D /home/postgres/data/standby 4. Try to reconnet ... gtm_ctl reconnect -Z gtm_proxy -D /home/postgres/data/gtm_proxy -o '-s localhost -t 7777' 5. BANG! WARNING: can not connect to GTM: Connection refused FATAL: Can not register Datanode on GTM WARNING: can not connect to GTM: Connection refused WARNING: can not connect to GTM: Connection refused WARNING: Xid is invalid. WARNING: can not connect to GTM: Connection refused WARNING: can not connect to GTM: Connection refused ERROR: GTM error, could not obtain snapshot ... -- Hitoshi HEMMI NTT Open Source Software Center hem...@la... (Please note that my address has changed.) Tel:(03)5860-5115 Fax:(03)5463-5490 |
|
From: Koichi S. <koi...@gm...> - 2012-07-09 06:35:11
|
No problem. Anyway, if misuse caused the crash, I have to fix it. Thank you; ---------- Koichi Suzuki 2012/7/9 Hitoshi HEMMI <hem...@la...>: > We might have made some mistakes about this. > We are now checking whether there really is a issue. > Could you please wait a while? > > Sincerely, > > -hemmi > > > Koichi Suzuki さんは書きました: >> Thank you Hemmi-san; >> >> I need some more question on this: >> >> pgxc_clean needs a port number and a host to specify what coordinator >> to connect. Did you use PGPORT and try to connect to a coordinator >> running at the local host? If not, then pgxc_clean cannot find a >> coordinator to connect to and pgxc_clean should fail. >> >> Regards; >> ---------- >> Koichi Suzuki >> >> >> 2012/7/5 Hitoshi HEMMI <hem...@la...>: >> >>> 1. Both of two option forms failed. >>> # pgxc_clean -a >>> # pgxc_clean -d postgres >>> >>> 2. Postgres-XC 1.0 on CentOS release 6.2 x86_64 compiled by gcc (GCC) 4.4.6 >>> 20110731 (Red Hat 4.4.6-3) >>> >>> 3. Please find atached file (core and executable of pgxc_clean included) >>> The core file is that of >>> # pgxc_clean -a >>> >>> Best; >>> >>> -hemmi >>> >>> Koichi Suzuki さんは書きました: >>> >>> >>>> This must be of another cause. >>>> >>>> Could you send the following information, if possible? >>>> >>>> 1. How to reproduce the problem, >>>> 2. The version, >>>> 3. back trace of the core >>>> >>>> Kind regards; >>>> ---------- >>>> Koichi Suzuki >>>> >>>> >>>> 2012/7/4 Hitoshi HEMMI <hem...@la...>: >>>> >>>> >>>>> We tested this patch, and found that the bug still existed. >>>>> Could you check it again? >>>>> >>>>> Thanks. >>>>> >>>>> -hemmi >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> Koichi Suzuki さんは書きました: >>>>> >>>>> >>>>>> Attached is a fix for this bug. >>>>>> ---------- >>>>>> Koichi Suzuki >>>>>> >>>>>> >>>>>> 2012/5/28 Koichi Suzuki <koi...@gm...>: >>>>>> >>>>>> >>>>>> >>>>>>> This will be fixed before V1.0 is out. >>>>>>> ---------- >>>>>>> Koichi Suzuki >>>>>>> >>>>>>> >>>>>>> 2012/5/28 Hitoshi HEMMI <hem...@la...>: >>>>>>> >>>>>>> >>>>>>> >>>>>>>> Hi, >>>>>>>> >>>>>>>> This one is about pgxc_clean. >>>>>>>> Is it obsolete? >>>>>>>> >>>>>>>> >>>>>>>> ============================================================================ >>>>>>>> POSTGRES-XC BUG REPORT TEMPLATE >>>>>>>> >>>>>>>> ============================================================================ >>>>>>>> >>>>>>>> Your name : Hitoshi Hemmi >>>>>>>> Your email address : hem...@la... >>>>>>>> >>>>>>>> >>>>>>>> System Configuration: >>>>>>>> --------------------- >>>>>>>> Architecture : x86_64 >>>>>>>> >>>>>>>> Operating Systems : >>>>>>>> A. CentOS release 6.2 >>>>>>>> B. RHEL5.7 >>>>>>>> (We tried in two OS-Compiler pairs.) >>>>>>>> >>>>>>>> Postgres-XC version : Postgres-XC 1.0beta2 >>>>>>>> >>>>>>>> Compilers used : >>>>>>>> A. gcc (GCC) 4.4.6 20110731 (Red Hat 4.4.6-3) >>>>>>>> B. gcc (GCC) 4.1.2 20080704 (Red Hat 4.1.2-51) >>>>>>>> >>>>>>>> >>>>>>>> Description of problems: >>>>>>>> ============================================== >>>>>>>> >>>>>>>> [postgres@localhost xc_bkup_test]$ pgxc_clean >>>>>>>> Segmentation fault >>>>>>>> >>>>>>>> >>>>>>>> #### ptxc_clean w/ --help option works >>>>>>>> [postgres@localhost ~]$ pgxc_clean --help >>>>>>>> pgxc_clean cleans up outstanding 2PCs after failed node is recovered. >>>>>>>> Usage: >>>>>>>> pgxc_clean [OPTION ...] [DBNAME [USERNAME]] >>>>>>>> ... >>>>>>>> >>>>>>>> ============================================== >>>>>>>> >>>>>>>> Thanks. >>>>>>>> >>>>>>>> -- >>>>>>>> Hitoshi HEMMI >>>>>>>> NTT Open Source Software Center >>>>>>>> hem...@la... >>>>>>>> (Please note that my address has changed.) >>>>>>>> Tel:(03)5860-5115 >>>>>>>> Fax:(03)5463-5490 >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> ------------------------------------------------------------------------------ >>>>>>>> Live Security Virtual Conference >>>>>>>> Exclusive live event will cover all the ways today's security and >>>>>>>> threat landscape has changed and how IT managers can respond. >>>>>>>> Discussions >>>>>>>> will include endpoint security, mobile security and the latest in >>>>>>>> malware >>>>>>>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >>>>>>>> _______________________________________________ >>>>>>>> Postgres-xc-bugs mailing list >>>>>>>> Pos...@li... >>>>>>>> https://lists.sourceforge.net/lists/listinfo/postgres-xc-bugs >>>>>>>> >>>>>>>> >>>>>>>> >>>>> -- >>>>> Hitoshi HEMMI >>>>> NTT Open Source Software Center >>>>> hem...@la... >>>>> (Please note that my address has changed.) >>>>> Tel:(03)5860-5115 >>>>> Fax:(03)5463-5490 >>>>> >>>>> >>>>> >>>>> ------------------------------------------------------------------------------ >>>>> Live Security Virtual Conference >>>>> Exclusive live event will cover all the ways today's security and >>>>> threat landscape has changed and how IT managers can respond. Discussions >>>>> will include endpoint security, mobile security and the latest in malware >>>>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >>>>> _______________________________________________ >>>>> Postgres-xc-bugs mailing list >>>>> Pos...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/postgres-xc-bugs >>>>> >>>>> >>>> >>>> >>> >>> -- >>> Hitoshi HEMMI >>> NTT Open Source Software Center >>> hem...@la... >>> (Please note that my address has changed.) >>> Tel:(03)5860-5115 >>> Fax:(03)5463-5490 >>> >>> >> >> > > > -- > Hitoshi HEMMI > NTT Open Source Software Center > hem...@la... > (Please note that my address has changed.) > Tel:(03)5860-5115 > Fax:(03)5463-5490 > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Postgres-xc-bugs mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-bugs |
10 messages has been excluded from this view by a project administrator.
